I recently came across a solution at http://evilgpo.blogspot.com/2013/01/group-policy-preferences-drive-maps-and.html
for possibly speeding up the logon process when a drive-mapping destination is not available. Using a wm ipingstatus check.
So when you're on a laptop remotely, off the domain, it will speed up the logon process.
However I am curious as to whether the home-drive path specified in Active Directory (H: drive in my case), when pointing to a network UNC path for the username, will slow down the logon process when you're on a laptop and off the domain? Or is that established as persistent and doesn't try to connect upon each reboot/relog?