SekeRob, could you please point me to a reference about project prioritization?
1] What are the parameters that govern what priority a project gets?
2a] If a cruncher has X number of projects, does the rule say, that each get 100/X %?
2b] What determines the exception(s), if any, to this rule?

Thanks
;

I would like the choice of auto-selecting which other project to run, should one of my profiles stop getting tasks from the selected projects;
a backup profile that kicks in if I run out of work.

Choosing to accept work from 'Other Projects' basically means you get what's most readily available, rather than whats best for those systems. Selecting to take work from other projects is not an option for some of my profiles. For example, a simple (slow) system, with several cores/threads, but limited RAM, slow/small HDD and network restrictions in place. Several projects would cause system/network problems if they started crunching other projects.
If I was able to configure backup projects for each profile, with say HCC or HCMD2 tasks, that would be better.
I don't see any reason why WCG could not ensure that at least one project with low system requirements is not available. So, even a system where you (a tech) could select which (limited resource) Project(s) were in the Default Profile, (say if you needed to do work on one of these projects).

ATM you can deselect all projects in a profile, or just select projects that don't have tasks. I'm not sure this makes any sense either (but might require the above). If someone does not want to run tasks they can just detach, select no more tasks, or suspend. Do you want systems attached to the project, continuously contacting the servers, but not getting any work?