Earlier quoted context omitted.
Well, it doesn't seem to happen in practice so it's either hard or there are no incentives to do it, or both. But that's the reality we live in.
Yeah fine, you're not wrong, but it's still worthwhile to understand why it's the reality we live in verses just taking a defeatist attitude. If it's just a matter of one engineer taking a couple weekends to change the situation, that's surely worth interrogating.
At the end of the day, if you don't have a datasheet and the vendor gives you the finger, you're always going to be running a rat race against them, struggling to support 10 year old hardware with free alternatives, and they'll always win because they control the playing field. Further analysis of this phenomena ("what is the root cause of this attitude, and why does our society allow it?") would require actually criticizing and analyzing software development in the grander context of workforce politics over the past, say, 40 to 50 years. Spoiler alert: doing this will probably make you depressed.