One thing I saw here that I don't think I agree with:
That's only true of a human with additional context checking the URL list. Ideally, MusicBrainz should allow a machine to serve only the relevant links, and in this case I still feel the most relevant level is often either the artist level or the full festival (or at least day) level, for festivals - reviewing a stage, for example, is rare (although I'm sure it does happen). IMO the main argument for individual artist concerts is that by being as fine-grained as possible it allows us to match to everyone else's systems and be semantic web glue (for example, setlist.fm has per-artist setlist pages).
I'm somewhat wary of having very specific guidelines for the title, because really event titles are a field that only exists because we needed to have something to fit the database schema. Originally the idea was to allow having events with no title at all unless they had a real title, and base the info (and displayed "title") on relationships. I still like that concept, and I'd much rather have a way to autogenerate titles for untitled events rather than having a very strongly enforced standard.
I definitely agree with listing the place as it was named at the time of the concert, but I think the best solution for that is to push MBS-9019. I've asked and it doesn't seem to involve a lot of work, so I'm hoping it can be one of the first tickets solved after the May schema change.