I completely agree with your last comment, though: systems suffer from weird bit-rot diseases. If you never reboot, you may find things challenging when you finally have to.
Disclosure: I work on the Ksplice team.
Step 1. Boot your version 1 kernel.
time passes, and version 2 is released
Step 2. Apply Ksplice updates to bring your kernel up to version 2.
Your system reboots (let's say due to a power failure):
Step 1. Boot your version 1 kernel. This boots because it's the same kernel you booted a year ago.
Step 2. (Before bringing up the network) Apply ksplice updates to bring your kernel to version 2. This works because you booted the same version 1 kernel, and the updates haven't changed either.
When he rebooted his machine (after almost a year) and it failed to come up, I got to mock him back. "So can you remember what changes you made... in the last year".
On the other hand, even though I've never used it, ksplice must be a nifty way to apply urgent updates between regularly scheduled reboots.
(1) the update could not be applied to the running instance, so you have to restart to put the update into service, and
(2) to demonstrate that the update did not break the ability of the thing to start.
This address #1. It does not address #2.
It is extremely annoying if something has run for a year with a couple dozen live updates applied without restarting and then you have to restart for some reason (power failure, perhaps), and then you discover that somewhere in the last year it lost the ability to start. I'd much rather discover that an update has introduced a problem with startup immediately after applying the update.
Restarting things should be a regular part of maintenance.