Hello David,
Glad to hear you are making changes in your NODE definitions to reduce the SAPI requests we send to JES to ask for SYSOUTs that are part of your criteria.
We go into a single thread in alphabetical ascending order by the NODE/ALIAS names asking for SYSOUTs to JES every time the timer set in XFERTIME= expires.
There are multi-threading input interfaces like NJE that could allow you transfer 8 SYSOUTs at the same time if you have that amount of SYSOUT Transmitters setup for your NJE definition.
Also you could use the pre JES spool SYSOUT Allocation Intercept to bring the file into CA Spool prior it is spooled to JES and leave XFER as a backup contingency for the output created on JES shared systems where CA Spool is not running.
However, this is only one aspect of CPU usage you can address since other tasks will require other changes documented in the Bet Practice guide for a better overall CPU usage.
As I said before there are no single commands to tell how much CPU a subtask is using other than reviewing a dump or dumps of the task taken at CPU spikes for analysis.
If you want to go that route David then please open a ticket so we can provide you with more info on what we need to give you a better review of your Mainframe CA Spool task CPU usage.
Regards, Cesar