What does snow do when new kext is added- beyond the -f command ??
 

What specific actions are taken by Snow when a new kext is found? What does it do that is different then a normal boot?

For example: It recognizes that there is a new kext in /System/Library/Extensions, and adds it to the mkext.
Whatever this process is in itself, the actions that it is taking, fixes a bug that I have.
Then, if I shutdown for 30 seconds, the bug comes back and I have to put a new kext in, and have it do this process again

How do I enable it to go through those process every boot?
And I don't mean -f, that doesn't do anything/

Reason I am asking, is I think I can fix my bug ig I get it to do that action every boot, and placing a new kext in every new time I turn on my computer has been driving me crazy

I dont know what it does exactly, its handled by kextd automatically, it launched kextcache when it finds a changed kext in /S/L/E, if you read the man page maybe you will find some clue. If you do "touch /System/Library/Extensions" you will trigger kextd cache rebuilding but I think it has to be done after the system is up.
Anyway whats the bug you have? Having to rebuild the cache constantly doesnt seem a solution. If you have a problem with a kext that crashes or unloads, you can use kextstat to find out which one it is.

I get system lag that makes computer unusable.

But time and time again, removing or adding a kext in s/l/e fixes it until I shutdown