I don't think the point is that this is causing wasted CPU cycles, it's that if something shows symptoms of being written by incompetent programmers, it's likely they were incompetent in many other ways.
Quality code is optimized based on what really matters, and I'm skeptical GC cycles really matter here.
Having an incremental CRI watch (vs poll) has been on the backlog for years, but correctness and features have been more important for most people.
Several people were looking at this recently as we were squeezing management pods + system processes onto two dedicated cores for telco/edge real-time use cases (the other tens of cores being reserved for workloads). It’s not that hard to fix, it’s just never been the top priority.
Real software has curves.