I should probably have made that clearer. There's obviously situations in which you want policy to differ between the login screen and an active session. The issue is whether you can configure those policies to be consistent with each other or not. For instance, if you can configure your login session to change cpufreq settings but can't configure your session to do so, you're probably going to find that odd. If you have both configured to suspend on lid close on battery and then find that one suspends if you close the lid and then unplug, and the other doesn't, that's going to cause you issues. Having different implementations makes it effectively impossible to ensure you have consistent behaviour.