But there are so few options available, at such a high cost, that nobody uses them.
Abstract interpretation / static analysis can detect lots of defects automatically.
Usually, the time required to properly setup and understand and refine the analysis will take most of the trial period.
These tools are better thought of in the long term, they may require some changes to coding style, and also some knowledge of the code itself.
While they are good for building defenses, they are not so effective for helping attackers. But in the end, yes, they _could_ be used for that.
Fire simulation modelling.
Computational GIS tooling (Hexagon et al)
Computational Algebra (eg Cayley|Magma)
Fireball monitoring, Square Kilometre Array processing, . . .
I'm struggling to recall anything I've worked on that didn't emphasis code correctness.
And regulated fields are a big market, not just the huge companies that work in this field (you can see a short list on the linked page), but also suppliers of these companies.