there are already several limitation how people use Bitcoin whether on protocol or node level. For example, minimum relay fee, minimum output amount and 80 bytes limit on OP_RETURN.
And that's fine. But if people are going to advocate for continually moving the goalposts on what those limits are, purely because they want to prevent a certain type of transaction, that's still a road to disaster in my view.
When everyone knows what the limits are, people are free to transact. And yes, some people will inevitably find methods of exploiting or abusing those limits. But if those limits keep getting tighter, to try and catch out the ones exploiting it, you'll also catch innocent parties who are suddenly outside of a limit they were previously within.
In that case, limiting Taproot script size (probably 10K bytes following which used as older script type) and maximum data can be pushed inside witness data (80 bytes or higher based on OP_RETURN) shouldn't be much problem. Although FWIW those number i mentioned wouldn't stop BRC-20 at all.
Miners will need to find other ways to make money, such as through higher transaction fees for high-priority transactions or through other services like staking or mining pools.
Or perhaps premium services which include non-standard TX such as TX which contain OP_RETURN data higher than 80 bytes.