For Command line actions, we can take over the SPAWN construction variable, which will call our own spawn function and then we can tailor the command and process output before returning back to scons.

For function actions we can duck-type the FunctionAction calls to execute from our own function.

Memory

For windows CommandAction can be monitored from python for a process using the peak_wset field:
https://psutil.readthedocs.io/en/latest/#psutil.Process.memory_info

Underlying windows specific information for peak_wset:
https://docs.microsoft.com/en-us/windows/win32/api/psapi/ns-psapi-process_memory_counters_ex?redirectedfrom=MSDN

CPU and duration should be completed from SERVER-67052

Json Format:

Note: for the action field, either the function name or command line will be used.
{
 build_tasks: [{
	 array_index: <int>(2),
	 outputs: [<str>](2),
	 inputs: [<str>](2),
	 action: <str>(2),
 cpu_time: <float>(2),
 mem_usage: <long>(2),
	 start_time: <datetime timestamp>(2),
	 end_time: <datetime timestamp>(2)
}]
}