I’m not in favor of generic expanded capabilities to the core protocol where we don’t know the limits of how they will be used. 

It would be better, IMHO, to pick specific use cases that the community wants and to then engineer the best, most limited change that meets that need. Vaults? Payment channels? Etc. We should design a change to do just that and only that. 

We need to learn our lesson with Taproot and discounted witness data. Devs didn’t realize how it would be used for spam. 

Devs aren’t omniscient and can’t predict all ways a change can be abused. Some of the abuses will even be indirect and attack the incentives underpinning key operations (like mining). Best to lock it down to reduce the attack surface area.