Well... Yes and no. We've had automated vuln scanning tools for at least 20 years and software developers really don't like using them.

A. Individual developers get sorta cheesed when an automated tool implies they wrote code with a TOCTOU or off-by-one error. They look for reasons to diminish anything a tool might say

B. Most of these tools do a very bad job of identifying architectural flaws. I spent a year trying to explain the Confused Deputy problem to my coworkers and why I wanted to use capability based security. They ripped it all out when I moved on to another team. Their product continues to have security problems because they forced the association of credentials between domains and didn't do a great job of it.

This is largely on me. I should have spent more time socializing the solution.

C. Management never wants to pay for tools they view as "vitamins" (as opposed to "pain killers.") This is mostly changing as ransomware attacks are on the rise.

But... Long story short... Yes... This will hopefully cause people to use scanning tools. But in a year they'll slack off and complain it's too expensive.