OK, I tested a few older revs to find which rev my nloader.log-corrupting-drive bug surfaced, and it appears to have been introduced in v1.66...
(Using a different HDD this time, just a 150 GB drive I had lying around, formatted to FAT32 with 32k clusters)
Using v1.65 resulted in a more perfectly normal nloader.log file, but then using v1.66 resulted in that weird broken nloader.log file I was getting with later revs, the file that only had 5 lines in it at any given time, along with Windows complaining about problems with the HDD like before. Using chkdsk to check for errors and recover lost chunks, it recovers a few more chunks (32kb in size), and sure enough, when viewing these recovered file chunks in a hex editor, each one seems to be bits if a file on my HDD, only the first kilobyte has been corrupted/overwritten by what seems to be the rest of what my nloader.log SHOULD be (so not counting the 5 lines in the ACTUAL nloader.log file, but everything after that), each recovered chunk with it's own corrupted nloader.log, for each run of nintendont that I ran before checking the HDD with my PC.
I do not know what files this is actually corrupting though, but right now I am worried that it could be corrupting anything on my HDD, and I am a bit scared that it could start to damage other things I have stored on my main HDD, like emunand, or Wii and GC save files, and other important files on there, therefore a bit scared to really continue using nintendont on my WiiU vWii for now...
I take it that regular Wii users would not have this issue, since nloader.log is sent to USB Gecko instead of FAT32 storage when run on Regular Wiis, correct?
Do any other WiiU Nintendont users or devs have this problem when running nintendont on WiiU vWii?