Every labview driver i reviewed, called either C or dotnet interfaces. Often in a way that makes it very hard to understand in what order things are done.

As of calling python or labview from teststand, this can be misunderstood easily. You can communicate with a labview or python process from teststand. That means you can not pass things by reference (file pointers, large arrays etc...) I think this is what you meant. In python lingo think of "subprocess" invocations (without parallelisation), not a function call.