I'd capture the data with a Performance Monitor "Data Collector Set", then either parse the output myself (if I wanted something quick-and-dirty) or run it through Microsoft's (PAL) tool. (I can't say that PAL is going to have a template for doing exactly what you want, but if you're willing to spend them time it's a pretty flexible tool.) Logging the "Process" object should get you what you need, in terms of raw data.
I lean toward PerfMon because, at the root of it, you're looking for time-series data. That's exactly what PerfMon does. The other tools you mentioned don't generate simple time-series data, and you'd need to do significant parsing of the output in order to get the data.
Your success with PerfMon is going to be based on parsing the data. Gathering the data is no problem, but you're probably going to have to do some work to get actionable information out of that data.
Edit:
The "Process" object doesn't get you user or the architecture (x64 vs x86) of the process. For that, I'd recommend enabling audit process tracking. Your event log will include the full path of the executable, and the user starting the process. It's more data to correlate, for sure, but it would get you what you need.