Wrong Warp with Farore's Wind

Farore's Wind return result per frame.

Function 800D61D0 is called whenever input to confirm a dialog is requested (A, B, C-Up). By breaking on this instruction, I was able to test each frame's result. Note that for blue warps, "frame" refers to the the blue warp timer's value (Instance + 0x182) when choosing to return to a FW point. Also note that the blue warp timer is updated before the textbox input request is performed. Testing was done on Fire Temple and Deku Tree's blue warps.

Child Blue Warps (Exit Frame 0x65):

0x00-0x59 //restore farore's wind point (0x00-0x58 untested but assumed the same)
0x5A-0x5A //wrong warp
0x5B-0x63 //destination, but with Farore's Wind coordinates
0x64-0x96 //wrong warp (0x65-0x95 untested but assumed the same)
0x97-0x97 //destination, but with Farore's Wind coordinates (normal void warp timing?)
0x98-0x99 //destination

Adult Blue Warps (Exit Frame 0xA1):

0x00-0x95 //restore farore's wind point (0x00-0x94 untested but assumed the same)
0x96-0x96 //wrong warp
0x97-0x9F //destination, but with Farore's Wind coordinates
0xA0-0xB4 //wrong warp
0xB5-0xB5 //destination, but with Farore's Wind coordinates
0xB6-0xB7 //destination
//End Game State

Farore's Wind "Void Warps":

0x00-0x00 //Confirmation Frame
0x01-0x01 //Nothing
0x02-0x02 //Zoneout Type = 3 (Farore's Wind), set the leave scene variable to 0x14, set next entrance index to FW destination
0x03-0x0A //Nothing. More importantly, the y < -4000 check does not occur
0x0B-0x0B //Copy next entrance index into current entrance index; Zoneout Type = 1 (Void), set leave scene variable to 0x14, set Next Entrance index to Void destination

Other Notes:

Noticing how confirming a Farore's Wind Return Point triggers an 0xB (11) frame sequence, you can see a consistent pattern across all of them.