Looking beyond listeners - Event driven customizations

For many years, I have had a few listeners employed to keep the system in check and save some time for my users. Its always been a battle between these customizations and breaking OOTB functionality. One that has been my mainstay has been a Rename Listener which propagates name changes from Parts to CAD docs and drawings. 

First it was the introduction of multi-object rename. Great improvement but broke the listener. I learned to decouple by pushing the act or propagation to a queue task. This allowed the rename action to complete and the queue triggered the associated object syncs. 

Now, looks like I hit a wall with that fix and Import from Spreadsheet jobs with Parts. These can be used to mass rename things if the name does not match the existing Part in the system. I can work around this but its problematic. Looks like something is modifying an queue task object which causes the dreaded stale object error.  

I am looking for a new way other than listeners to perform the original task of syncing names. What other approaches, more modern approaches are out there.  I know there are collectors on rename actions but this forces too much on the end user to get it right.  What other event driven customizations are out there in Windchill to decouple from the action?