Every linux distro that I worked with including slack had NTP configured because the h/w was unreliable. Regarding the many rtos systems I worked with, there was never a dependency on a h/w-based wall clock. Not saying there’s no such thing, but most prolly rely on an external references.
I can't think of many systems that would crater over a 61-second minute, then again, nothing I support these days considers time that critical. I have worked on systems where it would have mattered though. It was a really kick-ass fault tolerant unix box (Stratus) that processed and cut call detail records. Billing could easily have been impacted by something like that, but we had programmers who knew that, and actual test systems that we could test with.
This was back when Y2K was a thing, and we actually tested the Y2038 issue as well, when the unix 'time' counter rolls over. That had interesting results.
Speaking of which 2028 is coming.... glad I'll be retired by then.