This is a pet peeve for me, so feel free to ignore any excess vitriol.
If it's in the Management Suite directory, we're going to use it. Sooner or later, it'll need to run. When it does, and that AV client pops it for some stupid reason like "it wants to send email" or "that's not a word processor" or "this one piece of malicious code also uses TCP 5007", you'll get problems with your LANDesk installation. But you won't call Symantec or McAfee for support, because you already know they won't answer... instead, you'll call LANDesk, and it'll take us a while to find the problem because most of these tools don't log very well or ignore the exceptions unless they came from an administrator workstation or something else like that.
Whitelisting sucks. If you must use a whitelisting AV client at all, you should factor in an additional ongoing head count to maintain it, because keeping up with the changes required is a full-time job unless you start doing blanket exceptions. If you must use an AV client on the core, tell it to whitelist Program Files\LANDesk. If they won't let you do that, call your AV administrator any time that anything goes wrong and tell him that AV broke it until he can prove otherwise.
Working around the vitriol
i think you are asking about avoiding scanning what the LANDesk scanner is scanning to reduce load and to avoid the AV scanning every file that the scanner tries to scan? As Jack says, you should be able to exclude the LANDesk directories as the easiest way of doing this.
Mark Star - MarXtar LANDesk Enhancements
Home of Power State Notifier & Wake-On-WAN for LANDesk
I made these exclusions:
C:\Inetpub\wwwroot (Because IIS – Global.asa file)