Context matters here. While uPnP ones are not cleaned up is different problem than hotspot generated firewall rules and different still from connected routes, BTH, VPNs, etc.
For example OP's hotspot rules are not changeable since the rules change based on setting under /ip/hotspot, which is how you edit what goes into the hotspot's dynamic firewall rules. And if /ip/hotspot config doesn't allow what you need, you can add your own "static" rule before the hotspot chain gets invoked to exempt some host.
But generally speaking "edit dynamic object" is same disabling the feature that's creating the dynamic behavior, and adding your static config instead. Practically speaking, since RouterOS is creating the dynamic config internally, you run into needing to resolve what the user "edited" vs what some ROS feature's config want to "dynamically" configure – does RouterOS override your change or leave it as is after a reboot?
I just struggle with the use case, since if you want static config then do not use a feature that creates dynamic config. Not always possible, but allowing edit of dynamic config isn't the answer. For hotspot, the TV can be whitelisted etc. Or uPnP, it's whole function is to add dynamic dst-nat's since you may not want to add them statically (now they should get cleaned up, but that's seems like bug...). Or even BTH, you can use normal WG instead of you don't want dynamic config items.
i.e.
But I want to join the claims too. If we can't edit/remove the dynamic entities(objects) - then at least let us be able to disable them. To be able to create our own, suiting our configs.
What specific ones are you talking about?