It looks like Vulscan is the culprit judging from the wscfg32log that you attached to your case. You should be able to add the /offline command parameter (for vulscan) to the agent_ini, then rebuild your agent.
This confirms that the install is being held up 10 min by this action in vulscan. From the wscfg32 log:
12/11/2013 09:26:22.370 1444 2132 ntstacfgDlg.cpp 1480 INI: EXEC6=C:\Program Files (x86)\LANDesk\LDClient\vulscan.exe, /changesettingsnoreport, INSTALLONLY
12/11/2013 09:26:22.370 1444 2132 tokens.cpp 663 Starting process: C:\Program Files (x86)\LANDesk\LDClient\vulscan.exe /changesettingsnoreport
12/11/2013 09:36:25.701 1444 2132 tokens.cpp 687 Processes returned : 229835193
Modify the above BOLD swithch in the agent.INI to tell vulscan to run offline to avoid the delay.
Talk to your support rep if you have questions, I hope it works.