I've had co-workers report weird behavior when they did not reboot for weeks on end.
I use desktops and disable hibernate. A booted Windows is a minty-fresh Windows.
Couple things -- specifically responding to your post, and the general discussion with other posters.
For desktops, it is a much better idea to let them sleep for some limited time period -- a few hours -- with the power configuration set to hibernate after expiration of that time. Leaving the desktops to sleep for long periods -- I did it for one machine for days or weeks at a time -- will stress the unventilated PSU which continues to power the RAM.
So you could imagine a lot of weird behaviors for a machine asleep and not rebooted for weeks on end.
IF the hibernation occurs with good error-free hardware, you can raise the hiberfil.sys over and over through several sessions with no problem. It also makes it easier to schedule wakeups or wake-up initiated by another computer.
As for the TBWs occurring from hibernation, I was thinking that daily writes of between 8 and 16GB would pile up faster than I'd think, but writes to the hiberfil.sys may not involve the full size of the file. I limit my hiberfil.sys to 50% of RAM.
Looking at TBWs for all my SSDs new and old, they're all still relatively in their pre-school years of longevity.
Reformatting an SSD is the biggest hit a consumer-enthusiast workstation will take. There's plenty of ammo in the bandolier for even quite a few of those reformats, too.