Many people do something like this by creating a virtual switch and using that virtual switch as a "Restriction" in Basic Rule or as part of a required expression (or perhaps other feature if you want to be more selective about what you restrict) in Rule Machine.
For example, you can create a restriction that says the Basic Rule will only run if the virtual switch is on, and you can make a required expression in Rule Machine saying that the switch must be on -- both accomplishing the goal of not doing anything when it's off. Then you can just turn the switch on this time of year, turn it off when you're done, and the apps won't do anything in the meantime. And you don't have to go into every app every time to pause, disable, etc. the app after this (though you will, of course, have to go into each app to make the change to add the virtual switch as part of your automation once -- it can't read your mind).
Here's how I'm doing in in a Basic Rule where I want to disable the rule when my "Christmas Automations Enable" virtual switch that I created for this purpose is off (as it is most of the year):
Again, this is an example of what it looks like in this particular app. In RM, you could make a required expression instead, and most other apps have some similar feature to restrict or modify their behavior.
