Determine which vi is executing at runtime and read its block diagram

Question

I have a time-critical loop.  Within this loop, one of a set of
known VI's is chosen in a case statement.  Within each of those
VI's, data is decoded in a specific way.  I cannot modify these
VI's to make the information I need available, because it would
increase the amount of execution time of the tight loop.
What I need to do is write a new VI which will "read" the components of
the block diagram, so I can determine dynamically what code is being
run.  For example, if there are three blocks in the running VI
that extract an array element, I need to be able to determine the index
of the array elements being extracted.
I could re-encode all of this information in a new VI, but that would
generate a maintenance headache, because the decoding algorithms would
have to be kept identical for every incremental change.
Is it possible to "read" the contents of a VI from another VI without reverse-engineering the VI file binary format?

Answer 1

Actually, no.  I'm probably not being very clear.  I'm not
interested in looking at the values within the VI, I want to be able to
see what the VI is doing.  I don't want to see the result of
ExtractDataFromArray() (which I know is not a real function -- it was
just an example), that is, I DON'T want to see the values on a "wire"
during execution.
Rather, I want to know how many instances of a certain kind of sub-VI
are in a VI, I want to know how many instances of constants there are,
and which sub-VI's they are wired to.
I want to be able to find this information, essentially:
    In FOO.VI:
       bar.vi is called seven times, each time, the INPUT1 is wired to terminal 1,
        and for the 7 various instances, the values "1," "3," "12," "17," "23," "35," and "71" are wired to terminal 2.
In C-speak, I don't want to know the result of the calls to the imaginary function ExtractDataFromArray(),
rather, I want to know that it was called seven times, with the
arguments (&input1, 1), (&input1, 3), (&input1, 12), ...
And I don't care what was in &input1 when it was called, just THAT it was called.
Essentially, I want to be able to have one VI analyze another and determine what it does.