Bitcoin's only supported and sanction use case was always money. Read the white paper title.You can not use fake pubkeys to store a jpeg and claim it's a supported use case.You can not use fake scripthash to store a jpeg and claim it's a supported use case.jSegwit stands for Segregated Witness. It does not stand for Segregated Jpeg.Every spammer knows that the only supported use case is money. That's why they work so hard to make their spam look like a legit monetary transaction with fake pubkeys, fake scripthash, fake witness, and barely enough sats to skirt the dust limit.
you're framing the question wrong. the white paper is a proposal, not law. the 'supported use case' is literally whatever the consensus rules permit.
inscriptions work because taproot script paths allow it. are they using script hashes in an unanticipated way?
obviously. but calling them 'fake' is technically incorrect- they're valid scriptpubkeys committing to witness data, a feature enabled by segwit v1. the dust limit is a policy rule, easy to bypass.
the network validates scripts and signatures, it doesn't care about intent. if you want to call it a resource misuse, fine, but argue it correctly: it's about block space economics and miner incentives. the code is the law, and the law allows this.