I agree that 2 is nicest, and it would likely further the use of such scripts. One alternative or addition that I thought of would be for it to be something builders are authorised to do for ‘public’ building (perhaps the same for transparent exits and/or instance rooms, as they offer a common benefit). Of course that could introduce some friction into the process, and while it maybe provides a benefit for the realm, it doesn’t offer a material return for the tinkerer. 
This’d certainly help e.g. the fluff dispenser planned for the cloakroom; I was suggesting it more for the ‘noises’ case which is in the (unusual?) situation of having to listen for activity, just not the details of it (assuaging some concerns). (Though from an IC perspective, perhaps it’s not surprising if school is monitored…)
In that case, being able to set data per-room while sharing a script between rooms (attached to an area) would also make sense, as specific noises and their delay/chance are likely to differ between rooms, but the script doesn’t need to. The alternative being to have configuration embedded with the script, which seems inefficient and unwieldy to maintain (if you have 25 rooms, an update means 25 uploads? 25 server VMs?). I saw you have area and realm scripts on the roadmap, just something to consider for them.