A couple of pilots and I have been comparing notes on static exits that have not been "loaded" or "have not loaded their grid". Essentially what this means is, knowing I have 2 static exits, I scan the location of the exits, bookmark them, but do not warp-to the exit (not even warp and stop).
What we have collectively seen is that these exits do not abide by their otherwise-mandated lifespan (i.e. Max Stable Time). For example, my static LowSec Exit, an A239, should have a max lifetime of 24 hours. However, the A239 static exit has persisted in the same scanning location for nearly 3 days now, having not warped-to the location and by doing so loading the grid.
It appears that the exit timer does not really start until/unless you load the grid for that particular exit. It will eventually respawn elsewhere in your w-space, seemingly according to standard respawn conventions of 4-6 days.
This in itself does not really mean that much, but when you combine this fact with the circumstantial evidence that, by not loading the exit WH grid, the corresponding K162 it would otherwise be opening to another system is not actually occurring, then it becomes relevant. If there are no K162's and you have not loaded grid for the statics, then essentially it seems your W-space is marooned. Nothing keeping incoming K162's from forming, but if true, you need not worry about constantly closing that nasty nullsec static exit as long as you never load it's grid.
For example, using the dotlan maps to monitor my system traffic, I have identified that if no incoming K162's form AND if I never load the grids for the 2 static exits, I never get outside pilot traffic. I have only been accessing my static C2 lately and I close the exit once I am done working the adjoining system. In many days I can account for all of the dotlan jumps in my w-space based on my own jumps.
Continuing to gather data, but if true, it could simplify WH exit management.