What about the other cases I pointed out, like when combining with multiple conditions from the same object type, or involving system conditions that don't do any picking?
TBH I don't think this is going to happen, realistically. The event engine involves a large amount of complex code, internally there are several different types of conditions that work differently, many important conditions have custom coding for them, and code for OR blocks is highly complex and spread through it all. Even after many years we still occasionally get bug reports and have to tweak the implementation. The idea of adding even more OR logic to all that fills me with dread. Then there's the fact that it's adding a second alternative to an existing feature, which I generally think is the way to end up with messy and complicated software. Add on top of that that I get the impression different people have different views on how this should work, and it seems likely an alternate OR implementation will not fulfill everyone's wishes in every case, and so could end up as something people end up avoiding anyway. Altogether this kind of adds up to a worst case scenario for a feature suggestion.