Basically every deployed C codebase contains "undefined behavior".

Which is intended. Suggested reading: http://blog.regehr.org/archives/213

But I will still always argue that it's a bad trade-off to make compiler construction slightly easier at the expense of insecure code all over the place.

C isn't broken?

Why would you think it is?

Not memory safe, bad type system, terrible 'macro' system, no/minimal(C11) support for generics, minimal standard library, pretty verbose (it's hard to build any good abstractions), lack of functional programming support, undefined behavior. Dealing with dependencies and headers in any but the simplest of projects gets old really quickly. Just about bigger project I've seen abuses the language to some extent. The list goes on and on.

I apologize in advance but...

"necessity"... Surely not THE "necessity", mother of invention?

I guess that would absolutely give you a veto on other people "scratching their own itches".

Snark aside, the issue is surely whether, if designing C now, the last 40 years of programming language theory would not have some impact.