Your well intentioned attempt to classify a process by name won’t handle some real world problems. Assuming Apple doesn’t release more than 10 updates a year and they don’t add more than a dozen processes on average, you’ve got a massive effort to navigate what’s changing.
Worse, there’s nothing stopping a bad actor from naming their process after one you believe to be safe. There’s a long history of valid processes being (ab)used for bad intent.
I would instead encourage you to learn about code signing, risks and benefits of loading code outside the App Store model. Get some understanding of gatekeeper and Apple anti malware tools exist where they log status, updates and possible issues.
Protection starts at the core.
The technically sophisticated runtime protections in macOS work at the very core of your Mac to keep your system safe from malware. This starts with state-of-the-art antivirus software built in to block and remove malware. Technologies like XD (execute disable), ASLR (address space layout randomization), and SIP (system integrity protection) make it difficult for malware to do harm, and they ensure that processes with root permission cannot change critical system files.
Controlling what you install, not relaxing settings designed to help you secure your apps and getting educated on security hygiene (password and biometric mistakes people can make, update cadence, backups) is a realistic task for most. Manually consulting a list that’s crowd sourced to check for suspicious tasks is a canonical Sisyphean task in my experience.