I had some problems with VTUNE native analysis and using LD_LIBRARY_PATH to find libraries on the Phi.
I was trying to use VTUNE to analyze a native application. Having copied my executable and libiomp5.so to /tmp and set up LD_LIBRARY_PATH (as suggested here) I could log into mic0 and run my app. But, I noticed that VTUNE seemed to be completing it's runs in far less time than it should have. I then noticed that using "ssh mic0 /tmp/myapp" (which I'm guessing is kinda what VTUNE was doing) couldn't find libiomp5.so. After futzing around and finding that "ssh mic0 <cmd>" doesn't run any of the bash dot files (explained here) it became clear to me that trying to use LD_LIBRARY_PATH to find things like libiomp5.so isn't really the best solution. In the end I placed libiomp5.so in /lib64 and VTUNE can now profile my app.
I'm not sure what the underlying VTUNE mechanism is, or whether there's a better solution, but this seems to work. I was thrown off by the odd "bash" behavior so maybe this note will help save someone else a little time.