Not sure I'd agree, though it's a good blog post. It's been possible to accidentally create unspendable outputs in Bitcoin, since the beginning, and in various ways.

A common one in the early days was to pay to a p2pkh or p2sh output where nobody knows the preimage of the hash, making it unspendable. There are other ways to accidentally screw up like that. This is just another one in the list (using a 32 byte value in the scriptpubkey which is not actually a secp256k1 x-coordinate, and therefore not a valid pubkey serialization according to BIP340).

An interesting sidebar would be: people who decide to create taproot keys by just lopping off the starting '02' or '03' on a pre-taproot style key, will not encounter this failure mode, as at worst they only need to flip the sign of their private key to spend it. Using an invalid x-coordinate requires a more profound screw up than that.

This is from awhile ago and is accurate. The discussion found a bug in bitcoin core where it would incorrectly validate addresses like this as valid.