I'll stick with CurveCP, thanks. It works, it has the added "perk" of encryption, and it's not tied to a single application, like uTP.
Then again, if you tie something into an application that hundreds of thousands of people already use, like uTP is tied into a popular bittorrent client, you can then claim "Hundreds of thousands of people are using it, to carry major traffic."
Of course, from the perspective of a Bittorrent client author it's much easier to implement TCP-over-UDP than to depend upon raw socket support / install a custom congestion control algorithm into the OSes TCP stack.
If there was a generic utpclient/utpserver pair of applications that I could use to proxy non-uTP applications, as there is with CCP, I'd try using uTP/LEDBAT. But to my knowledge, there isn't.
Then again, if you tie something into an application that hundreds of thousands of people already use, like uTP is tied into a popular bittorrent client, you can then claim "Hundreds of thousands of people are using it, to carry major traffic."