TCMD has a lot of threads; I can't tell from that info which one you want. (And it would be a really, really bad idea to randomly turn off TCMD's housekeeping threads.)
I meant I turned off the display of the CPU usage on the TCMD status line not the thread. Does this stack trace tell you about the thread in question?
0 ntkrnlpa.exe!KeSetEvent+0x2a1
1 ntkrnlpa.exe!KeDelayExecutionThread+0x5cc
2 ntkrnlpa.exe!KeWaitForMutexObject+0x393
3 ntkrnlpa.exe!KiDeliverApc+0x664
4 ntkrnlpa.exe!KeRemoveQueueEx+0x990
5 ntkrnlpa.exe!KeDelayExecutionThread+0x5cc
6 ntkrnlpa.exe!KeWaitForMultipleObjects+0x538
7 ntkrnlpa.exe!IoSetIoCompletionEx+0x928
8 ntkrnlpa.exe!IoSetIoCompletionEx+0x695
9 ntkrnlpa.exe!ZwYieldExecution+0xb92
10 ntdll.dll!KiFastSystemCallRet
11 kernel32.dll!WaitForMultipleObjectsEx+0x8e
12 USER32.dll!GetWindowLongW+0x141
13 DUser.dll+0x1717
14 DUser.dll+0x1848
15 DUser.dll+0x14e9
16 USER32.dll!KillTimer+0x58
17 ntdll.dll!KiUserCallbackDispatcher+0x2e
18 tcmd.exe!CPUUsage+0x3c700
19 tcmd.exe!CPUUsage+0x2eda94
20 tcmd.exe!CPUUsage+0x175798
21 kernel32.dll!BaseThreadInitThunk+0x12
22 ntdll.dll!RtlInitializeExceptionChain+0xef
23 ntdll.dll!RtlInitializeExceptionChain+0xc2