I love CarPlay, but I do feel like I'm risking my family's life when it fails to connect and I'm left fiddling with it while driving. It seems like what GM's doing would at least eliminate that risk factor.
Wireless connectivity may be frustrating (though I've never had connectivity issues plugged in to the USB port), but this is a really bizarre framing.
Just pull over.
Next time, try holding Volume down+forward buttons.
That being said, Ford makes great vehicles, but terrible software. My car has so many stupid bugs (all just annoyances).
An alternative solution is to not have to deal with these bugs in the first place by eliminating that extra layer. Thats what I am proposing. Direct connection of the phone to an AUX port is not carplay. It is the app running directly on the phone with its own context. Is it 100% bug proof? no because only a paper map would solve that problem. But far more testing has been done on the apps running directly on the phone vs the phone having to connect through the manufacturer's implementation of Carplay.
Again, I have simply and clearly suggested that OP prioritize his family over his device. Anything else you've chosen to read into that is you wanting to be angry and refusing to read anything written as a result. Please take a deep breath.
Other implementations (looking at you Hyundai) crash requiring you to pull over, disconnect the phone, reboot the infotainment and then re-enter your navigation destination.
The best implementation is no carplay: instead use an AUX port and mount the phone on the dash.
Second best is Tesla's custom navigation. They do something other car companies should: use one of the million speakers in the car to focus on navigation directions while allowing audio content to continue playing on all the other speakers. Such a simple idea but so good.
My previous-gen Kia Sedona does this as well (at least when using the built-in maps).