Logistics for deregistering parachains in the era of Agile Coretime

With on-demand parachain functionality enabled by Agile Coretime on Polkadot, there will be a significant growth in the number of parachains registering a ParaID and their wasm code, which locks away several hundreds of DOT.

Currently, only the root origin is capable of deregistering a parachain that has produced blocks. For more context, please view this discussion on StackExchange.

The key argument presented in that discussion is that the parachain manager account should forego their privilege of deregistering the parachain if it has produced blocks, as it aligns with the principles of decentralized networks. Do we want to hold every on-demand parachain to this standard? In the current setup, each on-demand parachain’s deposit in DOT is held hostage till the lock is removed through Polkadot OpenGov. Please let me know if there is any other way to deregister parachain that does not involve governance.