Let's consider a sysadmin who says "I blacklisted this module, so we shall never see it on this system."

And then, some random service or cronjob goes down a list and "modprobes" things. Such as a vulnerability scanner.

So the kernel module got loaded by name, until the next reboot.

Yeah, it's another coincidence and another narrowing of the conditions by which this can be exploited. But it's correct to say that blacklisting modules is not the panacea or a 100% airtight solution.