Hi all. First-time poster here--- wanted to thank everyone in the above thread for sharing their experiences & solutions (as well as dead-end Genius Bar "support" experiences) as it has helped me understand what is happening with my system.
For the sake of contributing to the knowledge-base on this topic:
System: Nov 2020 iMac (Retina, 5K, 27", 3.8 GHz 8-core i7, 32 GB RAM, Radeon Pro 570 8 GB graphics.)
Issue: Unlike many of you, my GPU Kernel issues didn't begin out of the box. The issues arose _very suddenly_ in probably January of this year--- after about 13-15 months of heavy/daily usage w/o change in what I was doing.
I use multiple displays (1080p 24" Samsung, 27" 1080p Samsung) for multitasking. I'm a writer and often keep multiple windows of drafts, notes, or references up on the 27" Sam, primary document on the 24" Sam, and then native 5K 27" is typically for video content (Netflix, Hulu, YouTube, or local files through VLC, etc.). I use Google Chrome, and have way-too-many tabs open; often I'd have 5 or more tabs of video streaming at once (I have atypical sensory needs), such as multiple YouTube windows, or 5+ Twitch streams, etc. For more than a year, this was a totally fine usage with no issues. Then 2022 came in and had other ideas.
Quick note, that I did have issues with one (or both) of my external monitors "bouncing" its connection (HDMI to an Anker hub to USB-C to the computer), leaving the screen blank as though disconnected. Unplugging-and-then-replugging the HDMI cable typically did the trick, but it was "hair trigger" during this time: if the hub was moved or the plugs got even slightly tapped (such as when plugging in a thumb-drive beside them) this would bounce the connection again. This problem vanished, as far as I recall sort of all on its own, and then the OTHER issues (which brought me to this thread) arose.
The slow-downs and kernel_task thermal throttling made work on the system impossible. The "triggers" always involved some degree of heightened GPU activity -- video, crap like GIFs on Discord servers, and Facebook in Chrome -- and was resolvable (without a crash/shut-down) so long as I caught it in time, and suspended those processes. (Closing out the offending application/tab/window, or sometimes just pausing video for a bit, often made a difference for a little while. Resetting the system altogether, or bouncing Chrome -- in other words ending/terminating processes -- also worked, but the issue kept arising. It never occurred to me that this could be from multiple displays.)
Presently attempting to recreate the issue on just the native display: no issues. (Local HD video through VLC, multiple YouTube tabs, Netflix, all playing/streaming at highest quality available, plus Discord + Facebook, etc.) I'm keeping an eye on activity monitor, and ALL levels of CPU usage are staying significantly below concerning levels---I'm only a day into this test, but so far, this isolated the primary area of issue. I'll be buying the Dell D6000 (thanks for that!) as others have recommended, and seeing how that goes for me; will report results of that here (for future readers/trouble-shooters).
I have zero gaming, or Adobe, or graphics/video editing (or rasterizing, complex rendering, etc) applications running: very straight forward and isolated usages. Word processing, Discord, email, and Chrome. (FB is a notorious resource hog and that has often been the "straw to camel's back" for causing the kernel issue for me: if I had no FB tab open, and only video, it reduced instances of the issue by probably 50% or more, but FB on its own would not create the issue.)
[As an aside: I had similar issues with an external display on my 2013 MPB in 2019; at the time I had assumed that these issues were related to the age of the system, so I never committed serious effort to resolving it. (The triggers there were always involving an external display, and graphics-heavy stuff: in that cast, it was some Steam games, typically NWN:EE, and sometimes a Windows simulator (WINE, for running NWN Toolset on a Mac). I never tried to resolve those things, but may well give it a go through just to see if it happens to be the same thing as the iMac.]
Thanks again for such a thorough walk-through of similar/related issues. For now, I'm assuming that my issue is more closely related to what all of you are experiencing than not, whether or not it is exactly the same thing. Will update once I've got my D6000 and see what that does.