People would choose different because operating Raft/Paxos clusters at scale isn't fun. Also, scaling reads is the hard part! At this point the trade offs are pretty well known: you either send all reads to the leader and limit the leader's overall throughput or you pay the cost of reading from a majority.

Your opinions are very specific to using consensus in orchestrators and control planes but the overwhelming majority of writes and reads to a Paxos or Raft cluster are in much higher throughput and latency sensitive systems such as databases.

Indeed we don't need better consensus algorithms. We need to closely examine our problems and step down to weaker consistency models and protocols that aren't worse to operate than Raft/Paxos or harder for developers to program against where ever possible.