Not all of us run Log4OM (or even have a computer it’ll run on). I put my logs through TQSL manually, and usually create new locations as required because I’ve a habit of re-visiting locations and I figure it’s easier to find them in the list than to enter the data anew. It works well enough for me. But yes, up to a point, clunkiness in the logging sites could be smoothed over by clever code in the logging software. In a perfect world I’d select a bunch of QSOs in my logging program, tell it to send them to the logging sites (LotW, eQSL, ClubLog, QRZ, etc…), and have all the rest happen automagically (including downloading any QSL details), but this world ain’t anything close to perfect.
It works up to a point, but there are certainly some summits where the activation area is in more than one gridsquare (county, state, country, whatever), in which case the activator is the only accurate source of the information. In UK the common requests from chasers (at least on phone modes) are WAB and grid squares, and trig point IDs, so I try to have those noted in advance just in case I’m asked.