Thinking of the way the SU2POV exporter works gave me an idea.
The SU2POV exporter basically explodes all in the model when exporting so all groupings etc are lost, but creates a backup (kept in a specific place) of the original BEFORE exploding all.
What if a ruby is written that utelises the existing ruby (that seems to be working to satisfaction, except for the destructive bit) but creates a backup before the process gets underway and automatically restores the backup as the original afterwards? It might mean that you'll have to close / open SU between exports though, but only the scriptmasters will be able to tell us that.