Our prototype has this indeed automated.Generally: the hard part is the same in both cases - detecting where is the noise in the image. When you have a noise heatmap, next step is pretty trivial in both cases - either you throw more samples in the region, or you blur it more (yes, even the most advanced denoising basically just blurs the image with varying blur radius). This means that if one approach did not work in a particular scene, the other one will be unlikely to work too. We have the filtering done, and now we are trying our luck with the adaptivity. We will probably release both in daily builds soon, but only the adaptivity will be turned on by default (or maybe always-on), because it is so much simpler to use. There are no reasons why not use it. Same is not true for filtering.
