Bad leaders can ruin great teams and great leaders can turn around weak teams. I've seen/done it myself. Without fail, when I switch out a weak manager for a better one, the team improves. When groups have no manager they might produce, but usually not well or as well as they could.
Management isn't around because some conspiracy made by managers to perpetuate themselves, but because it works. No effective group of people is truly leaderless.
The problem likely goes all the way to the board of directors who should hold the CEO accountable to build a culture that doesn't let bad managers exist in the org (by coaching or removing them).
A lot of companies have this problem, and it's a major dysfunction, but make no mistake, it's :bad: managers you have a problem with, not "pure" ones. I know a ton of great non-tech leaders who do amazing work of leading technical teams because they build the team around that. You get the lead engineer(s) to run the tech leadership while empowering them with autonomy / resources / support and holding them constantly accountable to well defined goals.
Management isn't rocket science, it's just a lot of hard work and discipline. It is its own craft and a very challenging and rewarding one if it suits you.
Layoffs are an effect of organizational dysfunction. In which case, the responsibility lies squarely on the shoulders of management. It’s just that there is a perverse incentive structure in most corporations, so 10% of the team gets laid off to continue to pay for the exorbitant bonuses and lifestyles of management.
BTW, knowing where your code is and how to build it is important. It tells you basic health about your engineering process. A good technical manager instinctively knows that anyone should be able to build a product or there is something very wrong. A suit will delegate and hope everything is workings out. If you managed sausage factory and if you had no clue where your factory was, that would be odd. Right?
About the “hard decisions”, suits needs to hold them accountable for those results. This could be done either by getting mega salary cuts or even just resigning for producing a massive failure. I have rarely seen suits getting affected when they had to make “hard decisions”.
You judge the utility (or lack thereof) of these positions while never having had one yourself. Luckily, it's the top management of a company that choses who these are and not engineers.
It's clear from claims like "if 80% of those people disappeared you would see absolutely no change" that you have no idea what their role is.
When you say "most suits had no clue where source code existed" you just fail to realize that that's good. It's not their job to know this, it's an engineer's job.
You talk about their "known contribution" as if it's a general sentiment, but show no proof of it being other than your personal opinion.
In fact, it's clear from statements like " Another of their contribution was to do meetings with other suits at customers/partners" that you have no idea about how valuable talking to customers is for a company.
And tell me, in case you had to "make hard decisions" like "throwing 10% of team under the bus in form of layoffs" what would you do instead? That's exactly one of the cases where the skills of an engineer are the last a company needs.