I think this is somewhat of an XY Problem. You’ve come up with the way you think you want to solve a problem and have asked about that which closes off other possible solutions that might work better. For example:
So why have lots of different motions sensor rules? Why not have just the one rule to handle all the motion sensors? That would solve the problem (don’t want to do a lot of editing, duplicated code) and in fact improve the situation as you will end up with even fewer lines of code over all.
How about Design Pattern: Separation of Behaviors? I see you are already using TimeOfDay which is a special case of Separation of Behaviors. Create a Rule that changes when TimeOfDay and weather_forecasts0_condition changes and set a flag (variable or another Item) that your various Rules check instead?
Or, as has been suggested already, Reusable Functions: A simple lambda example with copious notes. I don’t thin a Script would work in this case because you can’t get a return value from a Script.
NOTE: In OH 2 that long sleep is a really bad idea. You should schedule a Timer instead.
There are a whole host of ways to solve this problem. Many are documented in Design Pattern: DRY, How Not to Repeat Yourself in Rules DSL.