I'm getting the feeling that what's really needed here is a review of Labview itself. I'd seriously recommend reviewing the tutorials on this website and elsewhere to understand all that Labview can do. Once you're comfortable with alot of basic Labview concepts, this should be a breeze for you (Regular Expressions notwithstanding).
No need for the sequence structure: In fact, as a rule, you should avoid it at all costs. What you want to do at a high level is make a VI for parsing each line of the input. You do this by putting your parsing VI in a while/for loop that is autoindexed on the array of command lines. Once you do that you can do alot of stuff. For instance, once you parse the data (and maybe turn it into a useful format... i.e. turning those text time stamps into numeric seconds, or milliseconds), still inside the for loop, you could then collect all the similar commands into seperate arrays. Then you can go through those arrays (with a different for loops) and subtract every pair of commands (which are the same) giving you the time in between each command start and command end for that command. A case structure based on the command is likely necessary for what you do, and as long as your commands are sufficiently predictable, you can wire the output of regular expression match for the command: (Cmdr2|...) to a case structure and then write in each command case to handle it differently.
There's probably like 100 more ways to do it. Depends on a lot of different factors.
