Okay. I've found something that, although it doesn't solve the fundamental problem with iconservicesagent, it can lessen the symptom:
This issue only affects movie files and, presumably icons. I have the Activity Monitor sitting in a corner of my screen, and I've been watching what happens to our favorite daemon. When I open or select the folder containing the movie files, iconservicesagent takes over and runs up the RAM. So yesterday, I opened did a large transfer of movie files from one external hard drive to another (I've been having separate problems with one of the drives). ISA started to go wild, as predicted. Then, in the Finder window, I selected another directory. Doing so took the Finder's "attention" away from the movie folder while the copying continued. So while the copying was going on in the background, I force quit ISA a few times, then it stopped and settled down into its rightful place near the bottom of the activity list. It stayed there for HOURS. I tried this again with the same result. So... what I learned is that if the target movie files (I'm assuming that certain icons are giving ISA some fits, but I've got hundreds of movie files, none of which have "custom icons") are not visible on the screen, ISA goes about doing other tasks, and the Finder ignores what's not visible. Weird. So I copied around 1.4 TB of movie files without any interruptions from Finder crashes or anything else.
No, it's not a software solution. ISA is still an undisciplined toddler that throws fits when it gets upset. But take away the sight of those movie icons from the Finder, and it doesn't react to what it doesn't see.
And thank you all for your input once again. I've got a feeling that the fundamental issue will be there for as long as Mojave is in play, and for as long as Apple's software engineers don't attack the issue. I'd also venture a guess that, since this issue has been going on since before Mojave, as the Discussion forums attest, it's likely that it will continue into the Catalina era. I'd be wonderfully surprised if the issue dissolves after Mojave.