There's some truth to that. My opinion:

There's tons of competing priorities with those mostly* in charge of maintaining the popular lightning implementations. And part of that is normal maintance, improvements on existing features, bug fixes, and non-protocol related features. Normal stuff you'd find anywhere, not to mention many other priorities not directly related to the specific lightning implementation. Like supporting services like Loop/Terminal (lnd), greenlight (cln), and phoenix (eclar). There's existing stuff with existing users to support at a pretty large scale as lightning is already.

It's not about ossifying, nobody wants that and they all improve things on the protocol level at the pace they can support, taking into consideration their level of interests in any few of the many enhancements that exist.

One of the exciting things about LDK's role in this is that they at least can take a step back and not have to maintain user-side binaries. Libraries focused on the protocol work and leave user support to developers. There might be some trade offs but I think in general it's the right approach letting protocol experts in this space focus on protocols, especially if that's where they find the most enjoyment. It's such a gift to have them and for them to excel in that area, and I think we'll see some great protocol enhancements we've been waiting for come out of it soon.