Let's just give you a brief explanation of what Hyperthreading is and how it works, and that should help you make a better decision.
In essence, hyperthreading is a way to let two processes/threads run on a single core. The way this is achieved is by letting a secondary thread use any parts of the core that is not in use by the first/primary thread. This effectively lets the entire core be used, not just whatever parts are needed by the current thread.
So just as a highly simplistic example, on an second or third gen Core i5/7 CPU you will have SSE, SSE2, SSE3, and SSE4 instructions. Let's say that you have one thread running on a core that is using SSE and SSE3 instructions. A second thread could run and use SSE2 and SSE4 instructions, but not SSE or SSE3.
That means you have to rely a bit on the logic in the CPU to correctly match threads with cores where they can make use of unused parts of the core. It also helps if the programmer of the game/app takes hyperthreading into account during development, but sadly this is pretty rare.
Based on that, hopefully you can make a better decision about whether or not hypethreading is something that is going to be of the added value for you.