The tuning assistant tries to estimate the performance impact due to that particular event using a simplistic model. Basically, if the trace cache occasionally has to operate from build mode (because of a trace cache miss), what fraction of the cycles (performance impact) are due to this particular situation, assuming trace cache miss is the sole cause of the performance impact.
As for the trace cache miss rate question. The answer depends on how you want to interpret the data. The more important question is what are you trying to determine and what are you going to do with the information. I suspect that the rate of micro-ops/op averaged over any program doesn't vary much so it may not matter.
If trace cache misses are estimated to be a signifcant issue for running your program I would reccomend identifying modules with relative high rates and recompiling them with profile guided feedback as that will allow the compiler to feed the processor a binary that is organized to better flow through your logical branching structure than what is being created by default
