Disconnect system drive that contains your macOS Mojave install from computer ( This is so that Windows does not overwrite existing macOS Mojave boot loader )

Proceed with a Windows 10 UEFI install.
After installation reconnect macOS Mojave Drive, the Windows installation should now be detected and usable in Clover.
If Windows 10 is not detected or able to boot, then verify you installed Windows 10 as UEFI and not MBR ----> ( Read step 2 - For a drive with Windows 10 installed )

OR

STEP 2 - Using a drive with Windows 10 already installed

Verify your Windows install is GPT / UEFI or MBR / Legacy BIOS.
If Windows install is GPT UEFI then Windows 10 install is ready to use at Clover boot menu, you should be able to boot into Windows directly from Clover boot screen.

But if Windows drive is detected at Clover boot screen, but when booting Windows you get a black screen with a cursor on the top left,
then this is most likely because Windows drive is MBR ( Legacy BIOS ). You can easily convert MBR to GPT using Windows MBR2GPT tool ( this saves hours work having to reinstall Windows 10 and setting up all your applications again )

I have been following the following thread to hackintosh my T460s:
but it's very long and hard to sort through, so I thought I'd start a new thread specifically for this issue

Personally, my model has been doing pretty good with just the T460 EFI from github. I did run the scripts to create and patch a new DSDT, though, after installing patchmatic and iasl. I also manually installed VooDooPS2Controller.kext by following the guide on RehabMan's git wiki.

I also re-installed my kexts from CLOVER/kexts/other using kext helper to build them into the kext cache

My only glaring issue is the touchpad. It's unusably bad, I've had to use a mouse which kinda sucks on a laptop.

It'll be really slow and then all of the sudden be really fast. It hangs and skips intermittently. Kind of hard to describe but it's {censored}.

This was spurred on from a discussion in the Clover General thread. Where there was a debate on bcdedit being able create/read/edit (U)EFI Boot entries. I didn't think it appropriate to post all this information there and somebody may want to make use of this and its likely to get lost in that massive thread.

Out of curiosity I decided to see if I could create an EFI entry using bcdedit. What can I say I like a challenge. Whilst is not a documented method by Microsoft, as it turns out in a round about way it IS possible to create an EFI entry using bcdedit and these are the steps I went through to add UEFI Shell located on a USB stick to the EFI entries.

Third party software is available that can create and edit UEFI entries from Windows with better support and more features. I'm just making this information available in case those options are unavailable.

DISCLAIMER - This is not a supported method. Use at your own risk. I recommend backing up your BCD/Firmware variables/settings beforehand.

1) Copy {bootmgr} entry.
C:\Windows\System32>bcdedit /copy {bootmgr} /d "UEFI Shell"
The entry was successfully copied to {34e8383c-73a7-11e9-9cb0-94de8078a7b5}.
2) Edit the new entry using the new GUID bcdedit generated in the copy step.
a) Set the device and path for UEFI shell on my USB stick.
bcdedit /set {34e8383d-73a7-11e9-9cb0-94de8078a7b5} device partition=G:
bcdedit /set {34e8383d-73a7-11e9-9cb0-94de8078a7b5} path \EFI\SHELL\SHELLX64.efi
b) Clean up some of the stuff that was copied from {bootmgr} (optional as far as I can tell, just makes things tidier in bcdedit)
3) Put the new EFI entry first in boot order. (optional)

After completing the steps above, here is what "bcdedit /enum firmware" shows:

I shutdown my computer and when I turned my computer back on it booted up into UEFI Shell. After exiting the shell my PC went on to boot Windows.
Here is the resulting dump using "bcfg boot dump -v" from that shell:

You may notice that the shell shows as "Windows Boot Manager" in the bcdedit output. This I believe is because of the "WINDOWS" at the beginning of the option data that bcdedit added to the EFI Boot entry. I also believe this why bcdedit shows my Windows 8 installation as "Firmware Application" because it has no option data. I don't know how to remove this data using bcdedit nor do I know how the option data, that bcdedit adds, will affect other EFI applications.

There might be a way to create the EFI entry without copying the Windows entry but if there is I'm unable to find any documentation on how one would do so. If you use the create command then it just puts it in the BCD and I'm unaware of a way to tell it to create it in EFI instead, other than by doing the above.