I had a similar problem with Parallels. I had merely thought the new version would improve performance, but it turns out that the old version caused problems. So I'm going to describe what I did. Also many CPU intensive tasks are launched by other programs, so merely doing a force quit will cause them to start up again.
The first thing is to open Activity Monitor, click on the CPU tab, and then click on the column marked "% CPU". If the tasks with highest CPU don't appear at the top, click on the column again.
In my case, I had four tasks marked BSDTAR at the top, with each using about 100% of a processor. (There are multiple processor cores, so the total CPU usage can be much more than 100%.)
I double clicked on the row at the top. This caused a small window to pop-up with the name of the process group, the parent process, and the user. It listed BASH as the parent process. Since neither BSDTAR or BASH was helpful, I clicked on the parent process.
The window now changed to show BASH as the process group and Parallels Toolkit as the parent process. This told me that Parallels toolkit was the problem. Since an update was available for Parallels, I purchased, downloaded, and installed the update. I then shut down the computer, waited 30 seconds, and then restarted. The parent process of Parallels Toolkit had been LAUNCHD, indicating that the program was started at boot time.
When the system finished booting and I logged in, I opened Activity Monitor and the four BSDTAR processes were gone.
If I had just killed the BSDTAR jobs, they would have simply restarted the next time I booted the system.
***
Other suggestions
Close all applications before shutting down the system. If a process is hung, it may not restart correctly after a reboot.
If the problem is with WiFi, go to the Security & Privacy option of System Preferences, go to the TCP-IP tab, and click on the Advanced button. If you delete entries from the list of access points (using the + and - buttons) for the networks that are giving you problems. The entry will be regenerated when you try to log back in, and this may fix the problem.
Safe reboot is a good way to clear problems. Close all the applications before you try the safe reboot.
If you open the Console application (/Applications/Utility/Console), you can look at the System Log. This may contain useful information.
If you see something about the volumes named Macintosh HD and Macintosh HD - Data, this is normal. Catalina has changed the structure of the root device.
If you see a list of disk usage by file type, remember that the names of the types do not represent actual directory or file names. If you see something marked as Other with over a hundred gigabytes, this is normal. It is actually part of the operating system files.