I'm going to answer my own question here:
After digging into the event/eventgroup/channel/alert system for the past hour, it seems a bit over-engineered. There might be a better way, but my easy answer for now is:
a) Locate the event type number associated with the troublesome events
# isi event events list -v |less
ID: 35.673107
Eventgroup ID: 751469
Event Type: 400130001
Message: Mount request from 11.22.33.44 for /blah_blah_blah failed with error: STATUS_NOT_FOUND
Devid: 35
Lnn: 34
Time: 2025-01-16T17:32:44
Severity: information
Value: 0.0
b) Suppress it
isi event suppress modify 400130001 --suppress true
c) Check your work:
isi event suppress list
ID Name
---------------------------------------
400050004 SW_CELOG_HEARTBEAT
400130001 SW_MOUNTD_CLIENT_MOUNT_FAILED
---------------------------------------
d) Undo the suppression if necessary
isi event suppress modify 400130001 --suppress false
e) ... Profit!