Well, different projects has different priorities, even all seems to be running as "idle".
Seti@home-cmd is running at 4, Folding3/genome2 is configurable to 4 or less, "classic" genome is 4, UD is running at 1 (was atleast last time I tried...)
2 projects with the same priority will share equal, while lower priority-projects will typically get less than 1 %.
So seti works great with folding/genome. 🙂
The Folding@home3/genome@home2-client can also be configured to only use max% of the cpu-power. If you for example puts 50% here, the client will never use more than 50% of the cpu-resources. If nothing else eats up the rest, the idle-process gets the other 50%... 😉 Alongside seti, I guess seti will get 75% in this case...