CPU Overload / Dropout detected with CPU at circa 5%

Hello everybody, I’m the OP.
I’m sorry I did not keep up with the thread and the many considered and thoughtful contributions. I’m maxed out on my day job, always knackered and struggle to find the time and energy to do the music-making stuff. I barely go into my personal email more than once or twice a month.
Anyway, many thanks for all of the contributions.

I am coming back to this issue now as I have a 4-day weekend so … let’s make some music (or at least try!)
Of course the issue was never solved. And at nearly 2am I’m p*ssed off at Cubase cos frankly it feels like it’s just a complete crock of ****.

Posting now because I just found here Cubase uses only 39% of CPU resources - #3 by mart a useful suggestion, and having done it I see the following whilst Cubase is running:

Now, once I close Cubase I see this:

Clearly (well, it seems clear to me, but I’m a bit drunk and maybe I’m wrong) there are 24 “thingies” available (“things” here are maybe cores; I’m a Java dev not a computer geek but the gist of it seems clear enough). Cubase chooses it seems to use (up to 100% of ) 2 of the 24 that are available (to be fair, it does seem to use maybe 5-20% of the rest), and it seems it pukes when either of those 2 get maxed out. Is my read correct? I could be wrong but it looks pretty clear.
If this is the case, is it a Cubase issue? Do other DAWs do this better?
This seems on the face of it (caveat: maybe I’m wrong) to be mental, almost a mentally retarded use of CPU resources. If there is no way to fix it (settings/config etc), and another DAW does it better, I’m off.