Capturing reads, writes, and CPU in SQL server replay Trace results

I'm trying to guide devs to use replay traces to A/B test code optimizations and their correlating database impact. In my sample I use the replay Trace template and while I can include CPU, reads, writes in the capture Trace, the only way I can gather these metrics in the replay results is running a second Trace to intercept that traffic.

Is there a way to modify the replay result template to include these fields? I'd think you'd be able to since you can get results, execution times, etc.