My suspicion is that this was either a CAN saturation issue (ie - infotainment started sending a high priority message which could reach powertrain CAN) or a state management issue (ie - infotainment sent a “put modules to sleep” or “wake modules” message which was not handled correctly and caused one or more modules to transition to an invalid state for driving).
The fact that this possible proves the point: OTA updates are dangerous and should be banned.
What I really think: my car shouldn't have any bullshit "modes" to select from. Tune it once at the factory to some reasonable compromise, and perhaps make certain settings writable through the OBD port, and that will be it.
At a bare minimum any EV driver is going to want two power delivery modes. Jeep people surely don't want to plug in an OBD dongle when they go off road.
Obviously no vehicle should be updated while in operation and all patches should be signed.
Obviously, "software update while traveling at highway speeds" is just rolling too many drama dice.
OTA is fine. Ideally parked, or minimally A/B on the firmware, new version only run on next startup.
This would also mean the A/B failover would need to identify the problem as a bad update rather than a bug that pops up minutes later.
Assuming the best, it might just be an extremely rare corner case that was unknown and inadequately covered in QA.
This stuff can get complicated, and cars are the most dangerous technology that is sold to retail customers.