I think lahra2ins and LAHRA2INS are handled differently by linux/unix (the printer)
Also, be advised that password fields get messed up on all Xerox devices when you use Chrome (and very current versions of EDGE browser now that its built on Chromium)
But the network traces will show the issue for sure
There is no chance the Fall Creators update is in any way relevant, the steps I provided work on literally every OS that exists today for SMB on the firmware that I linked for your machine if you follow the steps I provided. If you are using a DFS (Which you are not) there is another step that may have been needed, but that isn't worth going over because it isn't in any way relevant here because it doesn't apply to Windows 10 at all.
If you want to firmly place blame, start with the wireshark trace, which is done in the webui (CWIS) of the printer and filter it to port 445 to see all traffic between the printer and the PC.
This is a standard setup that we do for a lot of our users and this is the first time I've seen this issue. I'm inclined to blame the Fall Creators Update, but want to be sure I haven't missed a step somewhere, or there isn't some other update or something that could be causing this.
It's still exactly the same settings required in exactly the same order.
My linked post shows exactly how to get the username in proper formatting for every single scenario that can exist.