The summary is "your company may not yet be worthy of OKRs". This kind of has the whiff of other religious movements in tech like REST and Agile: if it's not working for you, you just aren't doing it right. Try harder and hope to one day be worthy.
The common thread is that they're frameworks which promise to be very general and be applicable everywhere, but which in practice "everyone does wrong".
If no one can actually successfully use your framework the right way, maybe the framework isn't as generally useful as it purports to be.
Having gone through scrum and OKRs I agree with the idea that people tend to sell them to be 'generally' useful at least on the surface.
But once we started doing training/testing towards scrum, it's very clear we needed change as an organization. Some people ended up leaving as a result because it's not everyone's cup of tea.
I can't say the same for OKRs because I joined and it was already in place pretty effectively, but I imagine it to be similar.