Agree that rollback capabilities would increase complexity. Perhaps the first step is to create a quicker deployment process (more votes required than normal) without restricting the change to rollbacks. Seems like this thread is suggesting the same.
I also think that adding distributeSupplierComp, distributeBorrowerComp, and claimComp to the set of functions that the existing Pause Guardian can control is the simplest and low risk change we can make right now to protect ourselves from future bugs related to COMP distributions. If others agree, I can put a PR together.