Having just watched the video, there are a couple of points which almost-immediately don't quite seem right to me, in this 'simulation', 'reconstruction' or 'lab test'.
At 1:32 to 1:38 we see a screenshot on a laptop, displaying what is likely to be APP (Accelerator Pedal Position) sensor 1 & 2 signals.
(Before we go any further, I'll state that I am not familiar with the actual Toyota setup, but similar setups on a variety of other manufacturer's products currently in use today)
The screenshot shows the signals suddenly snap from low throttle to WOT (Wide Open Throttle) but the ratio between 1 & 2 doesn't quite seem right, given the scale of the graph. Normally, the lower line would be 0V and the top line would be 5V. Sensor 1 normally produces voltages of exactly half that of sensor 2. So if sensor 2 shows 5V at WOT, sensor 1 should show 2.5V. Any other value (within some tolerances) should flag up a 1 & 2 correlation fault and store a DTC. (Diagnostic Trouble Code)
However, on the screen you will notice that on WOT, the upper trace is where you would expect 5V to be located, whilst the lower trace appears to be quite higher than the expected 2.5V....maybe 3.2V assuming a 5V scale. Again, a correlation issue should be detected and a DTC stored.
Normally, the ECU ECM PCM or whatever you want to call it, supplies a Vref of 5V. This Vref is closely monitored, since it supplies critical components with a known stable source. Deviation from this source should flag up a DTC...
For OBDII, there is the requirement that emissions-related problems illuminate a MIL (Malfunction Indicator Lamp) and generate a P0XXX DTC, which can be read out by any generic scan tool.
In addition to the mandatory OBDII P0XXX DTC's, there are also what are considered 'manufacturer-specific' DTC's, designated P1XXX, P2XXX, BXXXX, CXXXX and UXXXX, which usually require proprietary equipment to read out and interpret.
With the above said, at 2:40 to 2:54 where the 'scanner' was consulted for a DTC, you will possibly note that the equipment used appears to be a generic scan tool and not authorised Toyota diagnostic equipment.
Getting back to OBDII compliance, only P0XXX codes have to be available to generic scan tools.... on the vehicles I work with, APP DTC's are designated P2XXX....
Anyway, at 2:13 to 2:16, what is he doing? He sticks a banana plug into something...is he shorting the 5Vref to battery voltage? If he is, the APP sensor 1 & 2 voltages would surely be influenced but his generic scanner would likely not see the manufacturer-specific DTC's.....