If all you want to do is make sure the laptops are up-to-date you could just make sure the McAfeeHTTP repository is active in your site list. That way as long as the device is on-line then it will be up-to-date.
Making a laptop a SuperAgent is probably a bad idea. The Agent 4.6.0 product guide states "select a system (preferably a server) in each segment to host a SuperAgent". If a laptop is a SuperAgent and it's out of the office then no other computers in that SuperAgents assigned broadcast segment will recieve wake-ups calls.
You don't need zillions of repositories. Numerically having more than 1 repository per 200-500 machines is not a good idea. In fact, for my largest customers who have 100K endpoints most of them have 10 or less repositories. On average a single machine only needs about 200-300KB from a repository per day. The most superior type of repository is a web server. It need not be dedicated but simply a server internal to your organization that has excess capacity. Web servers support a large number of concurrent users and have high throughput. Super Agents may or may not depending entirely on the platform it is running upon.
Super Agents on laptops is a horrible idea. Laptops move and will provide highly unpredictable repository access.
Both of you pretty much confirmed my suspicions with the laptop idea. I really didn't think that was a feasible option since they move in and out of the network so much.
We don't have too many repositories right now (7), but we want to get out of the UNC path business since it's slow and cumbersome with SMB.
Besides the 4.6 agent product guide, any suggestions on other resources for further guidance?