I think he's asking a much more general question, Mathias.
If I'm understanding the meaning of your question, I think there's some confusion about how things work in HL. You can't directly disable scripts in HL, you have to change conditions on the pick that runs that eval script such that 1. the script turns itself off or 2. when running can't have an effect. The most common way to do this is by manipulating the tags on a pick.
For example 1, if you want to disable a class special, you assign a Helper.SpcDisable tag to it, and then the eval script it runs finds that tag and stops before doing anything.
For example 2, if you don't want the Druid class to forward the Hero.NoMetal tag to the hero, you can delete that tag before it is pushed to the hero.
A third way to accomplish something is to undo or compensate for it after it happens. That's not always ideal, but sometime it is convienant. The first advice I gave you, relating to the Druids inability to wear metal armor, is of this type. Why is it convienant? Because the tag is forwarded to the hero pretty early, so you could run your script at most priorities. Why is it not ideal? It's not specific to druids. Should a future class with a no metal restriction come along, it would lose the restriction from this as well. Why'd I think that didn't matter? The "not ideal" issue seemed unlikely to pass.