There is how the book I'm reading describe the insmod utility:

The program loads the module code and data into the kernel, which, in turn, performs a function similar to that of ld, in that it links any unresolved symbol in the module to the symbol table of the kernel. Unlike the linker, however, the kernel doesn’t modify the module’s disk file, but rather an in-memory copy.

It looks like it won't persist since it's in-memory, but I'm not sure.