This is currently the way MultiPing and PingPlotter work together, although MultiPing doesn't collect data in any greater detail than it displays.

When you find a problem in MultiPing, you can right-click on that hop and "Send data to PingPlotter". PingPlotter will open and you can resume tracing from there. The final destination latencies from MultiPing will be included and tracing will start at the point you moved the data over to PingPlotter.

Is that what you have in mind?