Agreed this is buggy behavior and hopefully it can be fixed. GPU Lightmass uses Intel’s Open Image Denoise library (as does the path tracer), but perhaps it is possible to prevent it from doing that by adjusting its options or how the data is fed to it, or perhaps a fix can come from the library itself.
We haven’t seen this come up before, so thanks for the test case.