Not really. These are a separate version of trackAction events, which are different from custom events (in a way). trackTimedActions are very unique in their reporting and behavior, and I'm trying to understand the actual use cases a bit better.
Events are instance based. They would be timestamped provided all criteria are met to fire the event.
So if events A -> B -> C are the ideal chronological order then you could segment for that flow or just report instances of each. (FYI the time stamp if trended would only allow an hourly granularity. If seconds are critical then the time of event itself occurring may need to be captured separately as well.
Out of curiosity can you expand on what it is your events are trying to capture? It could be an evar is of use here.