Could login toboggan coexist with lazy registration?

I've seen the idea of handling the 'authorization required' fo both modules (login toboggan and lazy registration) is implemented in the same way (probably one inherited this from the other). Can we find a different approach so both modules don't collapse, and also providing the user functionality expected..

Currently, both modules rape the 403 redirection from the main administration, removing this feature to the site administrator. Is there a kind of functionality that would expect both 403 handlers working? (lazyreg should work when no uid is available, but for already registered-logged-in users the 403 should still be available).

Can we define the way the 403 message should be managed for the lazy registration? I mean, when an anonymous user tries to create content will find the 403 message, as well as when trying to edit other user's information. Both 403 situations are quite different, and programatically it could be difficult to identify each other, but from the administration pov, we can define node/add/* 403 situation to be controlled by lazyreg, and forget about the rest..

In fact I'm not sure if can achieve the same functionality without controlling the 403 handler, just providing a link to "Test site" where the user will be created and logged in..

Any more ideas?