As stated before, there are errors that are thrown when you map areas with partial overlap. The database and most renderers are unable to figure out which is on "top" when they partially overlap. People do care and they do notice. It may not be right away, but it happens, especially when focused on resolving errors and ensuring a high quality map.

It is clear you are mapping for the renderer. There are many services that rely on OSM data, beyond just a little golf game, and it is important that the data follow certain guidelines to ensure consistency across all those swrvices.

There is no golf course where the fairway and greens co-exist in the same space. They touch, yes, but there is no small area (or corners) of the green where there is a fairway somehow underneath and coexisting in the same space.

I continue to remind people mapping golf courses to review this page on golf tags, especially the section on common pitfalls to avoid.  Specifically, you are mapping partial overlaps, which is very explicit and even has a photo!

https://wiki.openstreetmap.org/wiki/Tag:leisure%3Dgolf_course#:~:text=Overlapping%20green/fairway/rough%20polygons%20(see%20graphic%20below).

Further, problematic mappers who repeatedly map in poor quality with errors are documented and handled by the DWG:
https://wiki.openstreetmap.org/wiki/Problematic_mapping/golf