Managing (deleting) abandoned development work in production environment

Hello everyone - after many years of use, we seem to have a lot of old, retrieved update sets which are uncommitted in our production environment. This is all abandoned development, none of it is going to be committed in production.

This causes confusion and frustration with our developers and implementers...and I'd like to just "take out the trash" and mass delete all previewed and loaded (uncommitted) update sets on our "retrieved update sets" table (sys_remote_update_set).

...is this a safe practice? Is there any other archival/clean-up technique that would be better suited for this?

I'm thinking this is safe, because these are all uncommitted and the only risk would be in managing current development which is not yet deployed, but is still in progress, working towards deployment. I am mitigating that risk manually by setting a deployment freeze window.

Any input is appreciated!