I propose that general add-ins should not set the clock speed themselves, but instead have the users do it - even because certain users may not be OK with overclocking their calcs. And if a certain software must overclock to work, then add a warning which explicitly explains that the user must overclock the calc using Pover (or any other tool which may be developed in the future, at their choice), and then optionally also offers to do the overclocking.
I actually disagree. I think not only should they set it if needed, but should be regulated when the add-in starts and is interrupted. Non-overclocked add-ins should also lock in at 58MHz at the beginning if they don't want to be affected by Pover. I'll work on a set of routines to make all of this a lot easier.