I recently noticed that, according to the Core Temp gadget, the two Boinc jobs allowed to run on my PC always run on c0 and c1. It would seem to be healthier for the CPU if they moved to different cores and threads periodically. Is this something controlled by the CPU itself? I think this is likely, but thought I would ask. Is there a programmatic way to get this to happen? Thank you!

Log opening lines:
2023.06.02 7:38:40 AM | | Starting BOINC client version 7.20.2 for windows_x86_64
2023.06.02 7:38:41 AM | | log flags: file_xfer, sched_ops, task
2023.06.02 7:38:41 AM | | Libraries: libcurl/7.84.0-DEV Schannel zlib/1.2.12
2023.06.02 7:38:41 AM | | Data directory: E:\ProgramData\BOINC
2023.06.02 7:38:41 AM | | Running under account ncarter
2023.06.02 7:38:42 AM | | CUDA: NVIDIA GPU 0: NVIDIA GeForce GTX 1660 Ti (driver version 532.03, CUDA version 12.1, compute capability 7.5, 6144MB, 6144MB available, 5714 GFLOPS peak)
2023.06.02 7:38:42 AM | | OpenCL: NVIDIA GPU 0: NVIDIA GeForce GTX 1660 Ti (driver version 532.03, device version OpenCL 3.0 CUDA, 6144MB, 6144MB available, 5714 GFLOPS peak)
2023.06.02 7:38:42 AM | | Windows processor group 0: 16 processors
2023.06.02 7:38:42 AM | | Host name: carter-amd5
2023.06.02 7:38:42 AM | | Processor: 16 AuthenticAMD AMD Ryzen 7 3700X 8-Core Processor [Family 23 Model 113 Stepping 0]
2023.06.02 7:38:42 AM | | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 htt pni ssse3 fma cx16 sse4_1 sse4_2 movebe popcnt aes f16c rdrandsyscall nx lm avx avx2 svm sse4a osvw ibs skinit wdt tce topx page1gb rdtscp fsgsbase bmi1 smep bmi2
2023.06.02 7:38:42 AM | | OS: Microsoft Windows 10: Core x64 Edition, (10.00.19045.00)
2023.06.02 7:38:42 AM | | Memory: 31.92 GB physical, 36.67 GB virtual
2023.06.02 7:38:42 AM | | Disk: 3.64 TB total, 3.32 TB free
2023.06.02 7:38:42 AM | | Local time is UTC -5 hours
2023.06.02 7:38:42 AM | | No WSL found.
2023.06.02 7:38:42 AM | | VirtualBox version: 7.0.8
2023.06.02 7:38:42 AM | | Config: GUI RPC allowed from any host
2023.06.02 7:38:42 AM | World Community Grid | General prefs: from World Community Grid (last modified 19-Feb-2022 21:06:49)
2023.06.02 7:38:42 AM | World Community Grid | Computer location: home
2023.06.02 7:38:42 AM | World Community Grid | General prefs: no separate prefs for home; using your defaults
2023.06.02 7:38:42 AM | | Reading preferences override file
2023.06.02 7:38:42 AM | | Preferences:
2023.06.02 7:38:42 AM | | max memory usage when active: 26152.86 MB
2023.06.02 7:38:42 AM | | max memory usage when idle: 29421.97 MB
2023.06.02 7:39:16 AM | | max disk usage: 200.00 GB
2023.06.02 7:39:16 AM | | max CPUs used: 2
2023.06.02 7:39:16 AM | | suspend work if non-BOINC CPU load exceeds 35%
2023.06.02 7:39:16 AM | | (to change preferences, visit a project web site or select Preferences in the Manager)
2023.06.02 7:39:16 AM | | Setting up project and slot directories
2023.06.02 7:39:16 AM | | Checking active tasks
2023.06.02 7:39:16 AM | Rosetta@home | URL https://boinc.bakerlab.org/rosetta/; Computer ID 3726661; resource share 60
2023.06.02 7:39:16 AM | SiDock@home | URL https://www.sidock.si/sidock/; Computer ID 39259; resource share 100
2023.06.02 7:39:16 AM | World Community Grid | URL http://www.worldcommunitygrid.org/; Computer ID 5819606; resource share 100
2023.06.02 7:39:16 AM | | Setting up GUI RPC socket
2023.06.02 7:39:16 AM | | Checking presence of 293 project files

If there is a way to get tasks assigned to different cores in rotation a good idea. Swapping during computation would cause heating and cooling and this would I think actually shorten processor life more than keeping the tasks to the same cores.

I would be interested though in hearing some other views on this.

Modern CPUs have a built-in overheat protection.
Don't worry about that as long as you run a sufficient cooling solution.

The main reason to keep processes on distinct cores is to ensure a much better L3 CPU cache utilization.

Under Windows task scheduler and Ryzen cpus, the scheduler will schedule high intensity work to the two highest performing cores in the cpu. They are designated the gold and silver cores and their status is communicated to the OS scheduler by the cpu itself. In Windows utilities they are typically starred or notated which two cores are the best.

To get the work to move would require an OS that does not understand the preferred cores notation, like any Linux OS. Or use a third party scheduler to rotate work.