While I can't answer your question 100% because I haven't found or seen anything like chaining queries together to get results, I can offer a few suggestions.
I assume that you are already working with queries where you separate the criteria using the and/or options in the query builder so I won't go into that.
I have been playing with the same type of scenario with relative success. I have been playing with deploying a single batch file that does nothing really and all dialogue is suppressed. To that distribution package, I added all of the other apps as dependants in order of how they need to be installed. Works pretty good actually. I had to put in some detection logic for some of the installers that weren't the best. You could do the same to group together apps that apply to a certain HW platform or OS/SW config.
I also tried making a provisioning script that would install a list of apps. Its a little more brute force as far as installing apps goes, but it works well for base OS installs. Its pretty much the same idea as above, just more explicit.
Here is an article that describes what I am talking about.
Other than making a complicated query, you can use the "filter"... this might work, haven't tried it as fully as for what you want....
In the Network View (Not in a query, but in your standard Console view), to to Devices > My Devices
Create a new group for each of the existing queries you have
Now run each query and drag the resulting systems to the group that was created for it.
Now Create a query and filter it by adding each of the groups above that you created
What would be nice is if you could link a query to a Device Group and then run queries against that. MS's SMS has that ability and its something I've wished for in LANDesk.
JMac, you can filter by your own or the public groups that you create by clicking on the "filter" button in the query
True, but the groups are manually populated where as if a query was linked to it, it could be updated regularily and be prepopulated for when the next query(s) ran against it.
As others have indicated, you can create a complex query inside of LANDesk, or you can script the dection logic into the package using any scripting languages (Autoit, Vbscript, any repackager), or you can use the new ER system