You are wrong on this point. The prior cutscene stored is the title introduction which plays before file select.
This is definitely correct.
Sockfolder and I confirmed the theory that the previous cutscene watched before doing a wrong warp (both with a death and with BA Farore's Wind) affects the warp. Some of the previously noted crashes were no longer crashing, meaning that the values of every feasible cutscene need to be recorded and tested with all three warp locations, using every possible location > location combination. I say every feasible cutscene because some cutscenes like Kokori Emerald CS have multiple values (I think it has like 9, the value changes every time it transitions to a new area), so only the end value is going to be important. In an additional note to this, some cutscenes CAN have 2 different values, such as skipping ZL gives you the initial value, while watching the whole cutscene gives you the end value (because you transition to Hyrule Field with Impa). None of the blue warps will have more than one [relevant] value, because you can't skip the cutscene and still get the initial value, because it doesn't actually set it until you get into the Sacred Realm, or wherever.
I'm working on collecting a list of values for every [feasible] cutscene. I'll add it and it's values to the wrong warp page whenever it is finished, and then everyone with working knowledge of MHS can help start testing the locations again with the different cs values.
EDIT: The above also explains why it was reported the Deku > DC wrong warp didn't work on console and why the Fire > Forest wrong warp didn't work on emulator. Both were confirmed to work today by simply changing the previously watched cutscene value.