I think dealing with the latency of the current link it might be very difficult / risky (phone -> Tesla server -> car).
That makes sense. In my very limited experience, you have to keep your finger on the forward (or reverse) button very consistently. Otherwise it stops abruptly and it takes a while to re-initiate. The experience of latency seems to be entirely in the initiation. So I think you are saying that during motion the communication between phone and car is bluetooth.They don't have to go through the server once authorized. Bluetooth would be plenty fast. If not receiving consistent, redundant commands passing CRC it freezes and waits until the link is stable. Not that hard.