#12 is motivated by internal QA concerns, but would also be useful for users wanting to optimize their Backtrex behaviours. It could also help them identify inefficiencies in Backtrex.
The Backtrex.Profiler module is already public, but currently the set of frontends and their respective inputs isn't configurable.