Hey bzgnyc2, here is the activity from three hours after booting, without loading anything except iStat, TG Pro, Carbon Copy Cloner, Some Logitech app for my webcam, BetterDisplay, and Adobe Creative Cloud. Oh! And ClipMenu—an app that is really old but really, really useful.
View attachment 2487386
That's interesting especially 3 hours after booting. mediaanalysisd and mds_stores are still working up a storm. With VTDecoderXPCService throwing in for good measure. If I had to guess, Spotlight (mds) is scanning every photo/video it can find, using VTDecoderXPCService to decode videos, and mediaanalysisd to identify faces, objects, etc to create text searchable indexes for them.
Questions that come to mind:
-Do you have lots of photos/videos on your system? I haven't had this issue but either way I wouldn't think all this would run for so long unless you had more than a few.
-How long have they been there? Unless the videos recently created, I would think these already would have been indexed since your initial system installation/last major update unless your indexes got cleaned out (did you do the Safe Boot right before this? or is this just one of Spotlight's random index rebuilds)
-Do you need Spotlight and/or indexing of your photos/videos? If this indexing persists and/or causes other problems, you could disable altogether as fisherrman suggested or perhaps just your photos/videos depending on your needs
Although I find the Spotlight of recent versions of macOS less useful/reliable than earlier (as in I end up just doing a brute force search for files when it can't find something I know is there), I haven't yet given into disabling it completely. I have disabled it for select drives and work areas for files where I know it won't be useful but I leave it in general I guess I still have hope...
Another Macrumors member shared this link in another thread and was surprised to see Apple is still working on the basics:

Here's Why RAID Storage Users Should Definitely Upgrade to macOS 15 Sequoia and SoftRAID 8.3
We’ve been hard at work squashing bugs and verifying fixes for our RAID users on macOS. But to get all these improvements you gotta have macOS Sequoia.

The bug about unmounting is one that I've experienced back to at least Mojave so now curious to test the latest Sequoia. Maybe they did more than just load it up but with AI junk...
EDIT: And the only fault I'm seeing on console is
sharedcache fault 16:04:10.218235-0500 com.apple.WebKit.WebContent checkinWithServer Failed bootstrap_lookup2 for name of coreservicesd, kern_return_t=#1100/0x44c Permission denied name=com.apple.CoreServices.coreservicesd
Okay, I'm also seeing an error with imagent and siriinferenced. Maybe I should nuke Siri?
Are the "siriinferenced" errors and "imagent" in the same message or seem related or are they two independent recurring error messages?
"imagent" is related to instant messaging / Messages. Are you using that on your Mac? And if so, is there likely lots of videos/images coming through your text / iMessages?
siriinferenced may be related to the above indexing of videos and perhaps making Spotlight indexes accessible from Siri but hard to say based on Apple's documentation these days...
My general tendency is to disable things I don't want (e.g. Siri, all services under Sharing, Location Services, etc) but of course varies by needs/preferences.
However, it doesn't look like your logd/runningboardd were unusually active in the above. Before they seemed constantly active and I would have been concerned about repeating errors/warnings to the log. One or two here or there unless related to a specific issue you are having is normal. Unfortunately, the signal / noise ratio in the logs / Apple's Console isn't optimal but that's an issue beyond the scope of this thread...in the meantime, what I would say is if/when logd/runningboardd start showing constant CPU usage (in top or Activity Monitor), return to the Console to see if there is anything you can pick out to see what's driving that.
Last, I would say monitor the above mds/mediaanalysisd/etc and see if they ever comes to rest. If so, I bet you would actually see pretty reasonably %idle after that (not counting any Safari, etc you start when you actually want to get work done). The rest of the processes look pretty light. A few higher than I would expect (e.g. PerfPowerServices and searchpartyd) and a few I don't even know (e.g. PID=375 and PID=264) but not terrible. Maybe you would be at 98% idle at that point and if so I would be curious your CPU temperature under those circumstances.