If it happens consistently across "dozens to hundreds" of enterprise environments as stated by the GP and with apparently zero exceptions in which they remained simple then, while maybe not a technical certainty, it should be treated as a practical certainty.
Pointing out that it's probably caused by management is not really very useful since there are so few means available for line workers to fix their managers.
This is true, and I agree, but mis-attributing the problem is still not good.
After all, if (for instance) a new IDE plugin appeared that managed sprocs consistently with code and solved this problem, then we'd still face "sprocs are bad" criticism because the problem was mis-attributed.
Pointing out that it's probably caused by management is not really very useful since there are so few means available for line workers to fix their managers.