I mean, kernel modules don't just magically appear and install themselves
At least not until the next version of systemd is released.
It would only be "Planned Obsolescence" if the user was forced to install an iOS Upgrade. But they aren't; so it isn't.
App developers can be pretty quick to drop support for older versions of iOS. So while you are correct, you'll eventually have to bite the bullet and upgrade once you're not able to get any more apps. At least that was my experience. I held off upgrading until I wiped the phone to trade it for a non-Apple phone. When I flashed to the latest version of iOS before the trade-in, the phone became so laggy that it was nearly unusable. And that was with no apps installed as I had wiped it clean of apps and data.
Systemd takes a top-down approach, and while some may argue that it's design leaves a lot to be desired, that doesn't mean that a bottom-up approach is automatically better. Based on the dependency tree, this appears to be a project that started out with few requirements and quickly grew after it was deep in the implementation phase, which is a problem regardless of either development approach. And then you have just bone-headed moves on top of that such as using binary logging. In any event, it's being widely adopted, it's here to stay, and I'm sure it will continue to remain controversial.
So stop quibbling and use modern software.
Running this version of Chrome requires that I install a new OS which means that I need to back up all of my application settings spread out across the entire system, install the new OS, and then try to put all of the pieces together again. And that's if the new OS supports my old hardware. So it's not as easy as you make it out to be unless you're willing to pay for my new hardware.