--cpu-max-threads-hint has no effect on Ghostrider
**Describe the bug**
I am attempting to use XMRig on only 10 of my 12 available threads. "--cpu-max-threads-hint" seems to have no effect on ghostrider specifically.

**To Reproduce**
Attempt to use "rtm_ghostrider_example.cmd" with command line option --cpu-max-threads-hint=83.

**Expected behavior**
I was expecting XMRig to mine on only 10 of my 12 available threads. 83 was the closest integer to 10/12.

**Required data**
![image](https://user-images.githubusercontent.com/43998628/144640188-03dc718c-a62a-4399-a499-7ad1ce9cf8c6.png)
![image](https://user-images.githubusercontent.com/43998628/144641083-5b6529fc-5066-4216-ab3d-8cc484c93f18.png)


**Additional context**
I have read that it would be better to use the config.json instead of command line options to achieve my desired result. That does not seem to work for ghostrider, either. I know that the command line option only works when there is not an already existing profile in the config.json. I did indeed ensure that there was no ghostrider profile in my config.json when I was initially trying to use the command line option. After discovering that my desired result did not occur, I tried to use config.json to define the threads, like this: 
![image](https://user-images.githubusercontent.com/43998628/144640617-a540885e-e79d-472c-8fff-b8ac880e3713.png)
This still has no effect. No matter what, XMRig always runs on all threads with cpu usage maxed out. Am I just fundamentally not understanding something here?