What do we call all latent and non-detectable bugs?

I’m talking about, essentially all the non-functional type bugs I think. Google lists things like Latent bugs, dormant bugs, heisenbugs, masked bugs, and zero-day bugs. Which is a great way to start. So I’m thinking about all the bugs that customers will either be incredibly unlucky to find because they are either in unreachable or dead code-paths. Code that might be pruned by the building process even, code that is just plain sloppy and bad style, things that a linter would complain about. For example comparing a variable to const without the const being on the lefthand side, and all the way up to inefficient loop code that is unlikely to have impacts. Duplicated code, where the code is duplicated literally in 2 places for instance… I would like to also throw in any non-functional bugs you would not want to fix, because the fix would do nothing tangible, and would generate a huge code-diff that just messes up the blame history. Things that even unit tests are unlikely to detect.

Hidden performance bugs, and security bugs have their own spaces really, calling them invisible/undetectable bugs just feels wrong when many of them are visible with extreme code-review or linter tooling. Has anyone ever come across a good all-in-one category or name for bugs that are just so low risk they are not worth fixing unless the code-police come down hard?

What about emergent bugs? A bit like emergent requirements.