Maybe you have modified some TotalFinder resources?
TotalFinder 1.9+ newly checks code signatures of all its components. I decided to do that to prevent potential scenario when the SIP-circumventing TotalFinder's system component would be tricked to attempt to execute some spoofed code.
/Applications/Utilities/Console.app, filter the view with "Finder", force quit Finder.app via CMD+OPT+ESC and kill TotalFinder.app via Activity Monitor, then please launch
/Applications/TotalFinder.app and observe the log. There should be an exact reason what component failed to load due to "corruption".