In short, no.
If you read up on
SOS_SCHEDULER_YIELD, you’ll see that
SOS_SCHEDULER_YIELD is not necessarily indicative of CPU pressure.
Several parts of the description listed on that page are quoted here, to help explain. I suggest reading the rest for more/better context.
This wait type is when a thread was able to execute for its full thread quantum (4 milliseconds in all versions of SQL Server, unchangeable), and so voluntarily yielded the scheduler, moving to the bottom of the Runnable Queue in its scheduler.
The most common cause of SOS_SCHEDULER_YIELD waits that I see is queries doing scans of pages that are in memory and aren’t changing, hence there’s no contention for page access and the scanning thread can run until it exhausts its thread quantum.
One more thing to consider is whether your workload is running on a VM that’s experiencing delays because of the host being oversubscribed. This can elevate the number of SOS_SCHEDULER_YIELD waits