I did do a test, and precise/MakePrecise on the POM pixel depth offset output did fix the POM artifacts as well. But it also increased instruction count quite a bit.
https://docs.microsoft.com/en-us/win…3dhlsl/precise
It seems from that doc it may end up disabling fused multiply adds and stuff so those kind of optimizations may have to be explicitly put in. It would be nice if there was a way to tell it to still do arthimetic identity optimizations and stuff, but only in way that is the same between passes. I guess the reason it gets optimized differently is different register pressure and stuff between the base pass and the depth prepass?