Additionally I would suggest that if you move key business-process batch jobs to be controlled by CPS it becomes a very key system. In this case you don't want it tied to maintenance cycles and other impacts from other systems - it is best off isolated on it's own box I think.
Especially as you will probably want to do performance analysis on there encapsulating database layer, AS Java layer and CPS user config (filters, optimised usage, etc.).
I have certainly seen instances of CPS not only on it's own box, but installed on a HA solution as well, as it becomes a key component of the E2E business process set of batch jobs - running the BTC jobs that are a large part of the heart of core systems.