My suggestion would be to not use "setWorkflow(false)" nor "autoSysFields(false)" when you are updating a real production data as part of user deactivation process. Those methods are helpful in case you are mass-updating data to just fix one field value for example. But in standard business process dangerous - e.g., turning off business rules might end up that a) SLAs running on RITM will not be completed, b) Metric Instances on RITM might not be completed and so on... many data inconsistency issues might pop up.

If the only problem is that your name is there - which is probably because you deactivated the user in your session, and onAfter BR run also under your session, then try to decouple the actions of 1) who is deactivating the user, 2) who is updating the RITMs. You can try "Async BR" if that is decoupling it from your session, or you could generate an event (like "sys_user.deactivated") in onAfter BR and have "Script Action" to be executed out of that event - then it would probably run under "system". I did not test any of these, but maybe it can help you.

Regards,

Dominik