Okay, I’m willing to try/learn, as there is definitely much to learn here. I’ve uninstalled kernel-modules-hook because I wanted to prove my thought that another broken symlink would be the result; and perhaps also prove @andreas85 was right about the linux-modules-cleanup.service file belonging to kernel-modules-hook… and I scored a bingo!
I think this also suggests that the kernel-modules-hook install missed creating the symlink to run it’s service (or as @andreas85 pointed out, left the service disabled)… and that my $ systemctl enable linux-modules-cleanup.service command indeed would have corrected that miss.
So I am going to pause until the next kernel 5.15.x update so that I can see/confirm that “other default handlers” kicked in and pruned the previous 5.15 kernel’s modules folder.
What scares me about pursuing this option is one question/thought… I’m sure these packages exist because someone ran into an issue these packages resolved (i.e. kernel-modules-hook states that it “keeps your system fully functional after a kernel update”)… so what issues might I be opening myself up to?
Trying to think about why I might have a need for either of these applications, I came to one thought… that delaying rebooting after applying an update (perhaps when running a server) could have some consequences… and if that’s true, I’d never run into those consequences as I always reboot my desktop (not a server) after every major update I apply (and they usually request it).
One final question though… it feels right to drop these broken symlinks… any reason not to?