QuantumQuest - I think a lot of these items don't really show an appreciation for the challenges.
If you're looking to remove the last Exchange Server and you're still maintaining Hybrid Identity, you're not the "average" customer, in that situation. So, the expectation that you would need to prune AD of the related objects for the server in order to clean it up doesn't seem like a significant concern. At some point, there has to be a limit to what sort of things require some skills to manage something. This includes PowerShell or otherwise, as well. That doesn't mean tools can't be made, but it starts to get to the point of "If you see a need, fill the need".
If you want an ECP and still also need SMTP relay, then not eliminating your last Exchange Server is really the way to go.
The synchronization issue is far more difficult than you're giving credit. If you're still looking for AD to exist, AD should be the source of truth. If you notice how synchronization works in the other direction, Entra ID/Azure AD has always been a flat structure for customers. This is because synchronizing into another structure would require a lot of manual care and feeding... mapping OUs from one side to another, or mapping users specifically. If that is a concern, manually creating users on the other side might be less concern. If there are only a few things, changing the permissions to work with Entra ID/Azure AD is also a possibility which allows for the elimination of AD (many times easier said than done). Universal Print is one of those services available that could assist in that effort.