It appears the way in which you’re interested by it’s backward. One ought to make the case that it protected to take away a DoS restrict. Retaining it needs to be the default place. Particularly as different limits are being lifted.
As an illustration, and not using a stack component measurement restrict it might be doable to assemble a Script which makes use of ~4GB of reminiscence to validate by utilizing the next Tapscript:
<396000 bytes push> OP_3DUP OP_3DUP .. OP_3DUP
With 333 OP_3DUP
s this may create a stack with a thousand 3.96MB component, utilizing about 3.96GB of reminiscence simply to retailer these. After all there may be extra you may do, however a reminiscence blowup might be the obvious instance.