You can make the code more robust. For example, instead of a yes/no check, make the check come up with a symmetric crypto key to decrypt the next chunk of code (if it also passes a hash check). Glitches will end up generating garbage, and even if you successfully glitch the hash check, you're executing random garbage.

Of course, the challenge there is that you've merely eliminated one glitching candidate.

Stuxnet had code blocks that encrypted by a hash of target hardware identifiers. No way to know what all code is contained, until it happens to run on the target system.

https://blog.quarkslab.com/bradley-hash-and-decrypt-gauss-a-...