Kernel-mode exploit dev toolchains lack debugging parity with userland, making iteration 10-50x slower

Developing kernel exploits requires rebooting the target VM after every crash, reattaching the debugger, and restoring state -- a cycle that takes 2-5 minutes per iteration compared to 5 seconds for userland debugging. A single kernel exploit can take 200-500 iterations to stabilize, meaning weeks of wall-clock time spent watching VMs reboot. This persists because kernel debugging fundamentally requires a separate machine (or VM host) as the debugger, OS vendors intentionally make kernel debugging harder to raise the attacker's cost, and no one has built a snapshot-restore workflow for kernel exploit dev that matches userland tooling like rr or time-travel debugging.