I would check the following:

1. Check the %SYS.Task class with SQL but also do an Integrity check, to see if there are any errors on those globals that hold that task manager data.

2. if the "corrupted"/"copied" task (with $h=0) is the one that consume 100% of CPU, I would try to "re-schedule" it to see if the new "next date" is set to something else. If not, to delete (you don't need to re-create it, looks like 1001 is a copy of 1000)

3. Monitor the 100% CPU task (SMP or JOBEXAM) to try to understand at what commands it's "stuck" 

you need to have an object from the %Dictionary.CompiledClass not from "your" table/class. Then you will be able to access all those Methods, Triggers, Incidies and so on.

The code I gave is a working code, not a pseudo code.

SQL adaptive mode s not avail. on 2022.1.2 but only on 2023.1 (right)

%SYS>s Status=##Class(Config.SQL).Get(.Properties)
%SYS>zw Properties
Properties("ANSIPrecedence")=1
Properties("AdaptiveMode")=1
... 
Properties("TimePrecision")=0