I think this behavior is likely to disappear and be replaced by something closer to what you are asking for with ClasslistEditor3 (aka ClasslistManager).
The double step behavior was initially defined in the dawn of this century
when instructors were still extra cautious about pressing a button and making a mistake. :-) and in which every change of state of the webwork database had to be accomplished with a round trip submission of a form to the server.