Hi @Igor Gelin ,
Could you share us the scripts that you use. Did you check the CPU used for SQL 2016 from other method?
Quote from a similar thread;
>After talking with Microsoft Support a few times, they finally told me this is a bug.
>However, the product team said the algorithms for this particular counter in SQL Server 2016 are too complicated to fix. They will be updating the documentation to show that the counter is useless now.
Did you have any high CPU issues? To troubleshoot high CPU issues, we can use Windows task manager resource monitor or performance monitor or SQL Standard report or some DMVS, etc. Please refer to below blog to get detail troubleshoot steps.
SQL High CPU troubleshooting checklist
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".