I think for most things, this is actually a good way to see it: As a third leg on top of reviewing your code carefully and unit tests.
As you say, people will still make many mistakes in how they write their formal requirements, or miss things they care about.
For math this is not an issue, it's usually easy to check that the lean statement is exactly what you want. But for software, and many other real world applications, it's better thought of as a new orthogonal testing vector that everyone should be using.
Not sure about should, but as long as even modestly complex systems like the Signal communication protocol map into millions of lines of Lean, its pretty clear that not everyone will be able to use it. We still need better tools (tools better suited to our monkey brains).
One of the nice things about mathematical theories relevant to the real world (e.g. PA) is that, assuming the theory is consistent and sound in the standard model, confirming that a proof is correct is a purely mechanical procedure. Now Lean is built on the Calculus of Inductive Constructions (which can indirectly capture PA, but includes a lot more as well), but it's child's play to write a simple PA proof checker. It's probably a few hundred lines of Python, and even for something like a million line proof, confirming or refuting whether a proof is correct will take a few seconds tops.
The caveats in the article are indeed important (e.g., "Did your formal sentence in the language of first-order arithmetic actually capture what you intended"? "Is there a bug in your proof checker?"), but I'd label these more as human factors than math factors. I'm afraid the general public is starting to get the impression that "Lean-checked" is just another quality improvement, like reviewing your code carefully or adding some unit tests. It's not—it's totally different and I don't think we should add so many scary disclaimers as to dissuade further progress with formalization.