Thank you for the suggestion. Unfortunately, I have tried that and ran into issues. See the following post for background:
What I found was that even though I set up the tags to record based on a driven scanclass with a one shot configured, historical tag values in the set had a different timestamps (I had to print the millisecond and microseconds of each timestamp to discover the cause). It would be nice if there was an option to force the scanclass to use a single timestamp.