Theoretically, since some updates, Windows 10 should work with NFS.
My experience shows that 10 Enterprise eats NFS shares, Pro - freezes to the point of rescue mode and the only remedy is to remove the NFS services in this emergency mode.
The above is said about Windows 10 as NFS client.
It seems rather pointless to me to set Windows as an NFS server, stick with SMB and if you're adamant to use SMB v2/3+ shares without credentials, there is a registry crack/hack/fix for it. 
If your source is providing NFS natively,
it's better to set LE/CE to use NFS shares in OS - mount them on OS level.
Kodi has NFS functionality, but, IMHO, it's like an addon, which works relatively slower and buggier...
I understand that you are also in CoreElec team ...
Really?
If you forget/never connect to your network via the embedded WiFi adapter (presumably - wlan0),
and connect only through the external dongle (presumably - wlan1),
chances suddenly, without any manual intervention, internal adapter to spontaneously connect properly to the network, or interface enumeration to change,
are little to none. 
Check this, for example.
Just "forget" the WiFi network on the embedded interface, via LE proprietary menu, and connect to your WiFi through the external dongle.
Simple as that, using it on a daily basis, since the internal WiFi is too week for my needs.
Why don't you:
# adb connect <ipofyourboxhere>
from another device with ADB in your network,
and once successfully connected,
try
# adb reboot update
to see if it will boot from LE SD/TF card?
"adb reboot update"
from Android?
Is that ROM also working in the blue PCB S32-V6 with LPDDR3?
I would suggest to find a suitable Android ROM for your box (stock, preferably),
then edit it like suggested in this post - Remote power trouble - by injecting this u-boot, for example:
u-boot.bin@LPDDR3-792Mhz (Post #151)
Then flash it via USB Burning Tool/Burn Card Maker.
Keep the stock ROM at hand and beware that you might need to short-circuit the eMMc pins (while keeping the reset pressed all the time), in case you brick the box to a black one...
I would not recommend trying the abovementioned ROM on LPDDR3.
Apparently the u-boot here is for normal DDR3,
and there is an enourmous chance to brick the box if you flash it on LPDDR3 one.
This is no place to comment the "subtitle stutter" issue,
do not smudge the thread, please.
There's new development on my case:
With this build - CoreELEC-S912.arm-9.0-devel-1523265719 - the box works FLAWLESSLY!
Therefore,
here's a link to an amended Android ROM (Wisdom), in which the fixed u-boot.bin_DDR3@792Mhz has been already incorporated and it's been tested on green v2.2 H96Pro+ board:
S912_H96_3G_DDR34_171120_MAC_ubootfix.7z
Flash the ROM via USB Burning Tool v2.1.2 or Burn Card Maker v2.0.3 on your own risk, of course. 
Good luck! 
Thank you, @bumerc !
PayPal account for a small token of gratitude, please. 
I have flashed this u-boot via Android ROM customization method:
This time - there was no need to revive the box by short-circuiting certain pins on the eMMc...
However,
LE still cannot power up from the remote, once it has been powered down.
How can I gather any serial debug information for eventual troubleshooting further?
Thank you in advance!
P.S. I am using gxm_q200_3g.dtb on my green v2.2 board...
Looks like in my case part of the DIMMs is Micron and DDR3:
I've found this very handy because now I can do a clean SD card install and still have my addons. I have two s905x boxes and want to transfer the data that's on the internal memory of the first one to the other one. How can I achieve this?
Boot both boxes in LE.
Stop Kodi in both boxes.
scp -r all desired folders from the source box to the target box.
Reboot the target box, or just start Kodi again.
That's one way to do it.
