Honestly I can’t tell if you mean once a month is too often or not often enough. I’m still new around here. I ran Linux like 20 years ago before RHEL existed. Came back thanks to Co-Pilot and Recall. Linux has changed a lot and is way better.
What I mean is, that there are sometimes severe security issues that require immediate intervention (updating).
For such issues, be it on Arch Linux or Debian Stable (two very different approaches to update schedules/frequency), you would still get same-day-updates that are very important to apply as soon as possible.
As such, making your own schedule that differs from whatever distro’s dedicated update policy can be problematic if you aren’t aware of the risks and mitigate against them. If you do plan ahead of time how to mitigate such risks (as in my example of following CVE disclosures and acting on demand), then go ahead and adhere to whatever schedule works for you 
2 Likes