Running multiple Atlas@home has caused errors for me so I've limited to 1 via app_config with <max_concurrent...

This is working fine but I will still download 20 WUs based on the fact the machine in question has 24 threads. They sit idle for a long time, no problem, but I think they are factored into the scheduler in a way other than 1 max concurrent. Basically when I have atlas UNsuspended it counts as a lot of cpu time for the scheduler and other projects won't fetch much work. The machine doesn't run dry but whenever I update any project without atlas suspended/[no atlas work] it'll always say "not requesting CPU work, don't need"

It seemed like there would be an app_config argument to limit the total number tasks not just the max in progress but I can't find anything. Anyone have ideas or experience with something like this?