Examples I happened to stumble across:

@Legoktm did https://commons.wikimedia.org/w/index.php?title=Template:Cc-pd-mark-footer&diff=prev&oldid=951199902 on the strength of the sysadmin global group, and later admitted they were editing the wrong page: https://commons.wikimedia.org/wiki/Template_talk:Cc-pd-mark-footer#Change_to_interwiki_link

Also from Legoktm: https://en.wikipedia.org/w/index.php?title=MediaWiki:Gadget-formWizard/WikiProject_Latin_and_Hispanic_heritage/Join&diff=prev&oldid=1249177287 technically required interface admin rights and was only possible on the strength of the sysadmin global group.

@Soda did https://en.wikipedia.org/w/index.php?title=Wikipedia:Requests_for_oversight&diff=prev&oldid=1248181286 on the strength of the global interface editor group, and then later admitted they didn't realize the page was fully protected: https://en.wikipedia.org/wiki/Wikipedia_talk:Oversight#Requested_edit

To be clear, I'm not blaming either of you - just highlighting a process failure that should be addressed.

In T378886#10286594, @Pppery wrote:

To be clear, I'm not blaming either of you - just highlighting a process failure that should be addressed.

Neither case of mine was a process failure IMO.

@Legoktm did https://commons.wikimedia.org/w/index.php?title=Template:Cc-pd-mark-footer&diff=prev&oldid=951199902 on the strength of the sysadmin global group, and later admitted they were editing the wrong page: https://commons.wikimedia.org/wiki/Template_talk:Cc-pd-mark-footer#Change_to_interwiki_link

Yeah, I meant to edit the sandbox, but I was planning to edit the real template the next day, just wanted the train to move forward further so there was less chance of a rollback (but editing a 10M transclusion template an extra two times wasn't worth it). To be honest I was more thrown off by the lack of the colored background that enwp has for fully protected pages, and not seeing that on the Commons template made me think I was in fact editing the unprotected page.

Also from Legoktm: https://en.wikipedia.org/w/index.php?title=MediaWiki:Gadget-formWizard/WikiProject_Latin_and_Hispanic_heritage/Join&diff=prev&oldid=1249177287 technically required interface admin rights and was only possible on the strength of the sysadmin global group.

Also intentional. I think the premise, "Most large wikis have a culture, either explicitly or implicitly, of discouraging holders of certain global groups from performing certain actions using those rights" isn't exactly right. No one has ever complained about my global sysadmin edits on Commons, and the enwp policy says, "System administrators may use their global rights in whatever manner they deem necessary..."

I don't really have a stance on whether this is a good request or not, it just seems kind of annoying, especially for people who are primarily active in using their global rights (e.g. WMF staff, global sysops, global rollbackers, etc.).

This seems to me like minimal value for a lot of work, at least I don't see how it could be done without having to update every rights-related UI in existence.

Yeah, I kind of knew that - this was more of an idealistic ticket filing than something I actually expected to get done.

I kind of like this idea, there have been times where I had the option to do something in the interface, but I wasn't sure whether it was because of my local rights or the global interface-editor rights. That group comes with several broad permissions like being able to (un)protect pages, so I'm not always sure whether I'm supposed to be able to do the thing. I don't think I've made any edits I shouldn't have, but then, there's no way of knowing…

It's true though that this seems tricky to do. The only easy way would be to implement it like AbuseFilter warnings – where it just gives you an error the first time you try the action, then it lets it through – which would be quite unpleasant for the users. (And FWIW, AbuseFilter lets you filter actions like page deletion, so you could implement this on individual wikis, if you wanted to annoy some interface-editors. I encounter this sometimes with filters where someone forgot to add & action = 'edit'.)