We've been building up CI tooling on top of Nanoscope. The short term goal for this is: make sure that none of our internal libraries (analytics, experimentation, etc) contribute a significant percentage of the time it takes to respond to any tap in the app. We have a lot of internal mobile libraries, so preventing perf regressions in them is a big rock.
If our CI efforts prove stable, then what you're suggesting should also be possible, if I understand it correctly.
If our CI efforts prove stable, then what you're suggesting should also be possible, if I understand it correctly.