1. "I'm very familiar with how to properly spline golf courses since I do it to create professional 3D representations using matching elevation data."

For the purpose of the discussion I'm going to assume you are using TGC 2019 (I'm not sure if these comments apply to PGA Tour 2K23, so take them with a grain of salt if so.)

2. "Per the multi-polygon standards, complex shapes with many nodes should actually be omitted."

Exactly what "standards" are you referring to? Complex shapes are the very reason that multipolygons exist and should be used. You can find the use of multipolygons used by OSM written on the wiki at http://wiki.openstreetmap.org/wiki/Relation:multipolygon.

3. "Why? Because they cause rendering problems."

Rendering problems are an issue with third party apps/software and are no reason to use improper mapping to get around those issues. There is a common saying in OSM: "don't map for the renderer". That only leads to problems. You should address those bugs with your software vendor. We are aware that there is software called Chad's Tool that doesn't handle multipolygons correctly yet. There is a bug fix that has been written and submitted (https://github.com/chadrockey/TGC-Designer-Tools/pull/143) but has yet to be pulled in and tested. Maybe you could lend your voice to get this fix implemented by dropping a comment on the pull request. It will make multipolygons less of an issue for you and other users of the tool.

4. "Whomever wrote that wiki entry should probably actually use the various apps that utilize OSM as their source."

What is important to remember is that OSM is a community project that is used by thousands of different pieces of software and millions of users. The standards are well thought out and have evolved over decades to focus on getting core concepts right. If there are problems with software that uses OSM, those are best addressed with the makers of that software instead of trying to work around them (and possible introducing problems with other users of OSM data).