The 'global' application of this feature to ALL workspaces is obviously using extra CPU resources

My guess is that it is probably related to the program figuring out whether the horizontal prices-levels in the VERY different type charts are within the same chart, or not. Maybe this issue is why some users have been reporting some problems about MC being too slow?
This is just one more reason that this feature should be redesigned, as discussed at length in another topic.

Not everyone will quickly figure out that they just have to turn-off the tracking-mode, OR only use concurrent workspaces that are 'similar' in price levels, I would imagine.
