[BUG] v3.4.4.0 Beta: cpuThreads setting is ignored on Windows (Ryzen 9 5900X)

[Dekavv]

Describe the bug
The Qubic Client (v3.4.4.0 Beta) is ignoring the cpuThreads value defined in the appsettings.json file. Despite having a specific limit set, the client initializes the trainer with nearly all available threads.

Environment

• Client Version: 3.4.4.0 Beta.
• OS: Windows 10/11.
• CPU: AMD Ryzen 9 5900X (12-Core / 24-Threads).
• MSR MOD: Successfully applied (ryzen_19h preset).

Steps to Reproduce

1. Configure appsettings.json with the trainer block at the root level.
2. Set "cpuThreads": 20.
3. Run qli-Client.exe as Administrator.
4. Observe console logs: Setting CPU threads to: 23 and READY threads 24/24.

Actual Behavior
The client overrides the user configuration and sets the threads to 23, utilizing all 24 threads for training.

Expected Behavior
The client should respect the "cpuThreads": 20 setting to allow system stability.

Configuration Snippet (appsettings.json)

JSON
{
  "ClientSettings": {
    "poolAddress": "wss://wps.qubic.li/ws",
    "accessToken": "REDACTED",
    "alias": "qli_Ryzen",
    "pps": true
  },
  "trainer": {
    "cpu": true,
    "cpuVersion": "AVX2",
    "cpuThreads": 20,
    "gpu": false
  },
  "idling": {},
  "xmrSettings": {}
}