I'm not Ashley, but I couldn't imagine this happening without a large rewrite of how eventing works. Because the structure across events differs so vastly, Construct would have to be able to discern when and where this is appropriate in each event, if at all.
If you're having to write a whole many scenarios with like conditions, perhaps a more creative use of events is needed. Use loops, AND/OR, groups and sub events to optimize your code, loading as many actions to the same condition as possible. It takes a little practice and planning, but it's worth it in the end.
Otherwise, I feel you. I would like a feature such as this myself. In the cases where's I've had to use brute-force methods (such as within this young animation system) there have been times I'll have to take time to correct one mistake across perhaps 10 or more events.