DEFER on batched actions doesn't make sense

I am still using Actions 1 on a site and have numerous work arounds for this issue - mostly just posting to see if these issues were carried over to Action 2.

Actions has the concept of batched actions (i get this when assigning multiple actions to occur on a workflow transition). Then from the actions_do() function we get:

    // batch node functions to avoid unnecessary and costly node_load
    // and node_save for each action; only the last one will do node_save

to manage this, the actions_do function sets a param DEFER for all but the last action in the batch. And then certain actions like node_publish check DEFER and if set skip their node_save call.

this is all well and good.. but.. what about all the actions that don't do a node_save?? having any of these as last in chain and all the previous node affecting actions won't work... OOOPS!!

and, to make matters worse, their is no weighting concept for batched actions (this seems like a bigger issue all on its own); so even though they show in a certain order in the workflow actions page - they are still placed in alpha order and sure enough; actions_node_publish comes near the top.. and doesn't get to do its save.

lots of fixes for this, remove defer, support weighting but rather than hack these modules (since Actions 1 is mostly dead) i think easiest solution is to simply clone required actions (like publish and unpublish) and clone them with a name that ensures they come last in chain.

anyone know if this issue still exists in Actions 2?