Plugin uninstaller. Access during module shutdown == access violation.

If you need an example why, take a look at the Enhanced Input plugin. when you disable that plugin it doesn’t clean up, leaving the “player input” and “input component” property in the project settings on the enhanced input value. It could have, if they wrote an uninstaller, reverted back to the engine’s default. Not so nice. So is it possible to write such module uninstaller and inject it at a point it can still safely access modules it depends on to clean up there?