You're getting tricked by misinformation-- what I suspect is some intentional consensus cracking (especially since we know most if not all of the BRC-20 stuff is being funded by Ayre & related entities) though it might just be confusion.

This stuff doesn't have anything to do with taproot-- to prove this to yourself go start up node software from 2019 before the taproot bip was even proposed and observe that accepts this stuff just fine.

You could potentially attribute the attack to segwit in the sense that it increased the block size which made more room for junk but to the extent that your complaint is that fees have been driven up, the same attack would have worked prior to segwit.  It's also easy to see that people were embedding irrelevant data in Bitcoin long before segwit (fine example being the Bitcoin Whitepaper).

If you want to complain instead that the attack is bloating the blockchain on disk of archival nodes or that its increasing the data that must be transferred during IBD-- then it's fine to criticize segwit but otoh where the hell were you when there was extremely widespread demand for additional capacity? -- it's not like bloating up the chain is a surprising result: it's the reasonable and expected downside of increasing the capacity.

It's important when contemplating an attack to realize that the attackers have every reason to mislead about the nature of the attack and the enabling factors.