That said, FSD seems quite capable of routing around standing water in many cases (e.g. https://xcancel.com/planoken/status/2030754820462633031, https://www.reddit.com/r/TeslaFSD/comments/1pw9f2m/fsd_navig..., https://xcancel.com/BLKMDL3/status/1991862465328779317, https://xcancel.com/JVTacoma/status/2046313902749921638), so handling the remaining cases seems more like a model intelligence / data issue rather than a sensor limitation. Lidar beams generally bounce off mirrorlike surfaces without returning to the sensor, so I think all lidar would tell you about standing water is "there's something shiny/reflective within this region of the image", which you already know from cameras+headlights.
https://abc7news.com/post/san-francisco-leaders-press-waymo-...
Engineering hours are finite, so if they're spread across interpreting signals from two different sources, they might not go deep enough to make either one as good as it could be.
Having your engineering resources more focused on a particular approach might actually yield better results.
I say this as someone who's dealing with LiDAR + vision vs pure vision in a different domain, and at this point, I actually think our pure vision systems are better.
For very complex things like AVs, it is critically important to keep the number of such variables down, since each acts on complexity & workload not as an addition but more like a quadratic, or worse—combinatorial explosion.
Here the goal is avoiding driving into the water in the first place.