The use case I'm referring to is when the client must be sharded to avoid CPU or network or disk bottlenecks.
Run multiple Redis instances and use a simple hash based on whatever key you want to route messages and get the throughput you need. It's probably never going to be part of the core Redis logic but should be possible as a module to do the routing when used in a Redis cluster.
Doing it without server support is tricky.