I can report after a little bit over 36 hours of success after those STEPs, the problem has resurfaced and I've had to revert back to hibernation.
Good while it lasted but non the wiser on if its SW/HW. I'm tempted to think HW but surely if it was, then why would I have 1.5 days without incident (with heavy testing of both user and system initiated and different durations) and then all of a sudden,
come back. Clearly the DISM did something to stable a situation that affected me on over 90% of sleeps, so I'm still of the mind that it's SW related.
OBSERVATION:
Since I previously reported that the SFC and DISM initally worked (up to 36 hours) and then followed up with the above, I've noticed that one thing that has always seems strange is the Type Cover interaction with the display.
After a full reboot (from the start menu), if you disable all screen off, sleep and hibernation options from powercfg.cpl, the action of closing the screen atleast on the first attempt actually turns the screen off, or shifts it over to a second monitor
even though it's not supposed to. After a Winkey +P to reset the screen, this never happens until the next full reboot. So there appears to be some sort of bug between the cover and the display.
That got me thinking and I setup the setting like this

and lid function like this:

So what this allows me to do set sleep via the Start Menu so the Type Cover doesn't affect the screen (thats the theory anyway) ...and it's been stable so far. And incase the "nowake from sleep" happens again, the power button sets it to hibernate which
still seems to work when the screen is black. This then alllows me to bring the machine out of hibernate rather than hard reboot.
However, I've not yet have to use the power button to send into hibernate since this config (whilst using sleep from the start menu) seems to work for me everytime.
Test for yourselves and see if you also see some kind of success.