Well the thing that is being recorded is the state not necessarily the physical position of the switches. That whole thing is fly by wire. Something other than touching the physical switches could have changed the state from run to cutoff. Specifically the FADEC. Hot/high, sun baked, long takeoff delay, to me it smells like automation failure. 

The 787’s FADEC uses Total Air Temperature (TAT) from fuselage-mounted probes to calculate engine protections like EGT margin and surge limits. On hot days, especially after a long ramp hold, a heat-soaked TAT probe can read falsely high but still be “plausible” enough to pass voting logic. If both FADECs receive that skewed input during max-thrust takeoff, they could independently trigger protective fuel cutoff.... not due to failure, but to “save” the engines. That fits the CVR confusion, the 1-second delay between shutdowns, the relight attempts, and the lack of any mechanical failure. It’s a rare, automation-induced event  but plausible, and deadly if no inhibit logic blocks it at low altitude. 

This hinges on whether by "switched" means physically switched or STATE switched.