Yes, it will and there is nothing we can do about it. Apple can respond if there are enough complaints. We can influence its decisions.
Can and will are two different things.
Side story...
When I updated from Ventura to Sonoma on this pretty new Mac Studio, one of my USB peripherals stopped working properly. (I'll leave out the particulars.) As it happens, I'm friends with the guy who designed this particular peripheral device, so I asked him what was going on. He told me that he'd had another customer tell him about this.
So, he emailed the engineers at Apple he'd worked with on this and some other products. Probably an unauthorized backdoor approach, which is why I left out the particulars. They got back to him within a day to tell him that they had never heard about the issue, were personally concerned, and that they would try to sneak in a fix ASAP. These are engineers my friend had a good relationship with, and he doubted that they'd mislead him. They certainly hadn't in the past.
Now, what's that say? It says to me that the Apple corporate system is focused on new whatever, and that fixing stuff that broke along the way is a lower priority. In fact, as you found out, they have a kind of emergency room triage system that determines what the engineers even hear about. Lots of corporate resources are put into prioritizing what gets worked on.
My guess is that this won't be fixed soon because it isn't a high priority for what drives the management. The engineers might be all for getting it right, but they may not have even heard about the issue. If it hasn't been fixed by now, it may never be fixed.
Also, this may be considered a feature, not a bug!
Check this out:
Sonoma Memory Leak
Although not exactly the same thing, the behavior is pretty much the same. If you use Finder to look at a list of files in a folder, it often takes quite a while for the list to be populated if the folder has a lot of files in it. At least that's what I've found. But, if you go back to that same folder and look again two minutes later, the listing pops up almost instantly. Go back a few days later to do the same thing and it takes half of forever again. It could be that the same kind of action takes place as described in the Eclectic Light article linked to above. A system restart empties that cache in memory, so Finder has to scan the folder again rather than looking for a cache listing. That doesn't seem to take nearly as long as a cache scan. (Note - this is just supposition on my part, but the two issues seem really closely related. They emerged at the same time, too.)
Maybe a daily restart isn't the worst thing you can do. It cleans up some Mail app problems, too.
