This is much weaker claim than your original one (~"the market values popularity over technical features") and a much less controversial one.
> something like "the half-life of a fork is only X amount of time, so it's a very bad idea to try to pull one off".
> If you find that one of the forks still has, for example, 20% as much hash power as the other, you have disproved the claim.
Again, ETH was forked off the original Ethereum chain and won (it has ~98% hashrate) so it is not necessarily a bad idea to attempt one.
> There's no way [~10 year old Bitcoin 0.8.x nodes] are fully compatible.
You can download v0.8.1 here (https://github.com/bitcoin/bitcoin/releases/tag/v0.8.1) and it should be able to fully sync the Bitcoin blockchain (i.e. including blocks mined today). If you use older clients for mining you might generate blocks that are ignored by other miners but your old client will still keep in sync and follow the same correct chain. (Something that is not true for ETH or Bitcoin forks).
According to your link you can apparently sync even older clients (e.g. v0.3.24) if you take care of non-consensus related bug fixes that would otherwise crash your client.