I'm not fully okay with this, much like you, but I am sensitive to the point that spending to explicitly unimplemented opcodes to do anyonecanspend, is an appeal to undefined behavior being static. That means no more soft forks ever. So to protect Bitcoin, in case we are confronted with something that absolutely requires a softfork, if you want to donate coin, spend to OP_TRUE. Any undefined behavior is undefined.

If inscriptions were using undefined opcodes, witness programs or other things to put data on the chain, then I'd be okay with dropping support for these. But since they are not, it's just not feasible to prevent past usage.