I agree with Jesse. The option to completely disable GPU rendering is an important one to have, because nearly every inexplicable "glitch" I've experienced ever since GPUs in video editing software first started becoming a thing, has been due to seemingly random GPU issues. GPU drivers are not in the control of BMD, and there is so much fragmentation and rapidly changing things in GPU platforms and their associated APIs that it's not surprising that the deal with the devil you make in achieving fast GPU processing is in inherent instability, depending on the config.
Thousands of forum postings have been successfully answered with GPU-disabling as the stated solution to the problem. Adobe Premiere is just as--if not more--susceptible to this than Resolve is, so this is not a simple matter of "your GPU must suck". The fact that Adobe gives you the option of CPU only processing has saved my bacon way too many times to count.
The ability to completely bypass the GPU is something that I expect in any software that professes itself to be for "professionals". I cannot afford to miss a deadline because a render keeps glitching for some unknown reason, and it turns out it was because GPU processing was the cause of the glitch. If the renders are 10 times slower, I really don't care, because that's a lot better than not being able to render
at all.
Much like how passenger airliners have a dinky little
ram air turbine as a last-ditch power source in the event of an emergency, CPU-only processing and rendering needs to be there as a failsafe in an app like Resolve, because people's livelihoods depend on delivering projects on time.
Resolve Studio 18.0.2 / Decklink Mini Monitor / 14" 2021 Macbook Pro Max (macOS 12.5.1, M1 Max) / 32GB RAM