There's definitely potential to do well on latency, if for example you have a server in NYC and your client has FIOS the inherent network latency could be 3ms and the only challenge is the encode/decode latency. It's possible Mighty has done something better, but every other remote desktop system I've tested spends more time on encode/decode than in the network, while claiming they're great (without giving numbers).
If you have figured out encode/decode latency, show me a high speed video (including the user's hands, not a screen recording) of say a Macbook on residential internet in NYC separate from your servers clicking things, compared to that Macbook running Chrome locally. Your numbers will almost certainly be worse for local interactions like typing in a text box, but you can show how it's better for things like clicking links.
Another issue other desktop streaming systems have is that video compression makes text ugly, especially when scrolling. This isn't as big of a deal for the game streaming systems but is noticeable on a retina display desktop. It's plausible Mighty has the codec settings cranked up enough so this isn't an issue though.