Thanks for sending it. It was huge, but I wasn't really able to tell what is causing the issue. It doesn't look like any totalfinder functions are doing some busy work on sampled stack traces.
But I noticed that you have also loaded com.infinitelabs.FinderExt. Generally it is not good idea to mix multiple Finder extensions from different parties. Could you please try to run it without it?
Also that information that the TotalFinder's tabs plugin is causing this issue is interesting. This narrowed down our search surface. Btw. you should also try to close tabs one by one and observe if that fixes the issue. I'd like to know which tab is causing this. It must be some edge case because I don't hear people complaining about CPU usage these days.