Answer
No — status/state flows for built-in pages are fixed in the framework code and can't be reconfigured or reversed, including via a direct Modify__ API call attempting to force the state backward. This is deliberate: a forward status transition typically triggers other side-effect logic beyond just updating the status field itself, so simply forcing the status value backward wouldn't correctly undo everything that happened during the original forward transition. To see exactly which forward transitions are actually allowed from a given status for a specific LU, inspect that LU's own Finite_State_Events__ function (or the underlying Finite_State_Machine___ logic, which is harder to read directly) in Developer Studio — it defines the complete, fixed set of valid next-states for each current status.