rsession-arm64 maxes out core AFTER execution for 5+ min on M1 CPUs in macOS versions -- console is unresponsive -- REOPENED

Two more things come to mind:

One possibility is that RStudio is having trouble with certain features or settings on your system. For instance, some users have reported issues with RStudio's rendering engine on macOS, which can be resolved by forcing RStudio to use software rendering. As a workaround, you can try changing this with Tools -> Global Options ... -> General -> Advanced -> OS Integration -> Rendering Engine [See this post] (RStudio Mac OS X 10.15.7 Crashes Everytime).

Another potential issue could be related to RStudio's diagnostics or linting features. There have been reports of RStudio's linter causing the console to stop executing code. As a workaround, you can try disabling R diagnostics in RStudio's settings: Tools -> Global Options... -> Code -> Diagnostics [See this issue report]
(Console stops executing any code with R 4.3 underscores · Issue #13091 · rstudio/rstudio · GitHub).