AFAIK the saved data that LKGC uses is dynamically updated after each successful boot regardless of whether SR is enabled or not. The problem it has for general systems problem solving is it only has a limited timeframe where the 'last known' might still be useful. Because once you get to a desktop (even a screwed up desktop) that becomes your current last known 'good' config.
SR was created to get around this problem since SR tracks key registry data plus a whole lot more, making for a higher chance of getting a good outcome.
So for dealing with an unsuccessful bootup that's keeping you from getting to the desktop LKGC works pretty well. I've had about an 80% success rate with it for that. But if you do get to the desktop, and hang once you're there, your only options are to either do a safe boot and try to fix whatever the problem is, or do an SR if you're really stumped.
Note: I don't know if it's true or not, but I was told that immediately rebooting and seeing a problem go away following a system update isn't unusual. That trick works for a JOOTT situation whenever a system update didn't completely or successfully install. Supposedly there's a built-in mechanism for checking, and if Windows detects an update didn't complete, it will rerun the update prior to fully booting up and: "problem solved."
Makes sense if it really is so.