This approach is outdated with the dual boot bios since they're really dual architecture UEFI implementations.
That's to say, you can use a regular x64 distro that comes with an EFI bootloader on it's install media by doing the following on the T01:
1. Flash dual boot bios.
2. Shrink the windows partition from windows to make room.
3. modify the ESP so fs0:\EFI\Intel\efilinux.efi points to a valid efi x64 binary. Just copy and rename a 64bit efi shell. You can also use rEFInd for a nice looking menu or Clover for mouse support.
4. Reboot to the dual bios' built-in bootmenu and reset to the x64 modules by selecting the Android icon.
5. Enter the UEFI setup (pressing the del key on boot) with the install media in the usb and choose to boot it. You can also chain load from the EFI shell or rEFInd but that's unnecessary.
6. After installation, the installer should have placed a grub efi bootloader somewhere in the ESP. just copying it over fs0:\EFI\Intel\efilinux.efi should boot you directly into your distro on reset to Android. You can also use whatever you used earlier to chainload the grub loader or directly boot the kernel if the file system is supported but that's redundant unless you're triple booting or running some specific distro that's lacking in an EFI boot loader for some reason.
Regardless, Using the x64 UEFI cuts back on distribution size and opens up the distro choices considerably since many distribution only package x64 nowadays.
Edit: Forgot to mention the dual boot bios solves the backspace bug properly.
Also, you'd want to additionally deploy shell efi binaries in fs0:\Shell.efi and fs0:\Shellx64.efi so the bios option to boot to EFI shell works. It's useful if the windows BCD gets corrupt since you can use the shell to chainload the recovery windows efi to fix it. You couldn't have done this with the older bioses since the backspace bug made the efi shell unusable which prompted a few of the posts in this forum.
2nd edit: It seems there's a bug in WinToAnd.exe which allows you to reset into x64, and get stuck there This could be quite a scary problem since it locks you out of windows.
However, there's a way to work around it. I've reversed the binary and figured out it writes to an EFI NVRAM store variable called BootSelectVariable. The way to get out of the x64 is to dump the variable in the efishell, hex edit it's value (a 4byte), reinsert the dump, and reset. It's all done in the shell. So far, I've figured out the following values:
The 32bit menu is 0x80 00 00 00 ,
32bit disabled menu is 0x00 00 00 00 .
64bit disabled menu and 64bit menu are unknown. The default for any value not previously mentioned seems to be disabled 64bit menu. Which, I learned the hard way
Regardless, if anyone is dual booting, even with the official android, I highly recommend familiarizing oneself with the efi shell
Edit: The reversed windows implementation: https://github.com/RamKromberg/toggleBootSelectVariable/blob/master/toggleBootSelectVariable.c
Under linux and EFI it's easier to script something.