Earlier quoted context omitted.
Sure, but you're in control, and can decide to do what's best for you and your organization. Taking on the technical debt of allowing your dependencies to get further and further behind isn't a decision I usually make, but it can be a valid one depending on the individual circumstances.
I mean, you aren't wrong. But this is akin to saying you don't need a memory safe language, because you can decide what is best for your applications memory needs. That is, I think the ask is more of "why haven't we come up with something that is a bit better at mitigating risks, here?"
Software engineering is complex. Some of the challenges are simply irreducible.
I believe this is one of them.