Well under some circumstances
Yes on high latency connections this could bring a considerably improvement. However it would require a new protocol, kinda an TCPwR (Transmission Control Protocol with Redundancy).
There are 2 Problems with this:
1. It won't go through unmodified NAT.
2. It can be hard to implement.
The first problem is particularly bad with "carrier grade NAT" you commonly have on high latency mobile connections, or mid latency consumer connections.
The second one is evident if you look at real life implementations of TCP/IP stacks. There will are ones, particularly in embedded systems still having severe problems. For example the Nucleus one just tends to drop connections without telling the application about it. Adding more complexity will cause lots of problems.
Maybe one sensible way of doing it would be to extend TCP in some way so connections could easily fall back.