A number of issues with killing random stuff that you don't know what it is...

Each process running is doing something. If you kill it, whatever that something is won't be working anymore. So before you start killing random things, you should find out what they are doing and what service they are providing.

Many processes are started by and monitored by sytsemd, so if you kill them, systemd will just restart them. So killing them might not just disrupt what they are doing, but it might be useless as they might be restarted.

You specifically ask about snapd. No, snapd is not just used to install snap files. It maintains the snap environment, so all snap based software would malfunction if you killed snapd. If you want to find out if you really need it, run snap list to find out what snaps you have installed. If you don't need any of them, you could probably uninstall snapd. (apt remove snapd)

You say that you have multiple 'python' processes. This doesn't really say much, because python is an interpreter, so the real program running is a python program whose name you haven't mentioned. Many parts of linux are written in python, so killing those could cause many problems.

Rather than killing random processes you found, a better approach to sliming down your system would be to start by looking at what services systemd is starting using systemctl list-unit-files and browse through the enabled services and determine what each one does. For instance, the command systemctl status apache2.service would tell you if that service is running, and the Docs: line has a link you can look at if you don't know what that service is. If you decide you don't want a service, you can temporarily stop it with systemctl stop ... or permanently with systemctl disable --now ...

You could also outright remove software you don't need with apt remove... but you should also carefully read what else gets removed before you tell it to go ahead and do it to make sure you are not doing something silly like removing your entire graphical interface software suite or something else you care about. You can find what package a file is installed by with dpkg -S /path/to/file and get a description of the package with apt show packagename... so you can pick through packages to see what they do before you remove them.

A number of issues with killing random stuff that you don't know what it is...

Each process running is doing something. If you kill it, whatever that something is won't be working anymore. So before you start killing random things, you should find out what they are doing and what service they are providing.

Many processes are started by and monitored by systemd, so if you kill them, systemd will just restart them. So killing them might not just disrupt what they are doing, but it might be useless as they might be restarted.

You specifically ask about snapd. No, snapd is not just used to install snap files. It maintains the snap environment, so all snap based software would malfunction if you killed snapd. If you want to find out if you really need it, run snap list to find out what snaps you have installed. If you don't need any of them, you could probably uninstall snapd. (apt remove snapd)

You say that you have multiple 'python' processes. This doesn't really say much, because python is an interpreter, so the real program running is a python program whose name you haven't mentioned. Many parts of linux are written in python, so killing those could cause many problems.

Rather than killing random processes you found, a better approach to sliming down your system would be to start by looking at what services systemd is starting using systemctl list-unit-files and browse through the enabled services and determine what each one does. For instance, the command systemctl status apache2.service would tell you if that service is running, and the Docs: line has a link you can look at if you don't know what that service is. If you decide you don't want a service, you can temporarily stop it with systemctl stop ... or permanently with systemctl disable --now ...

You could also outright remove software you don't need with apt remove... but you should also carefully read what else gets removed before you tell it to go ahead and do it to make sure you are not doing something silly like removing your entire graphical interface software suite or something else you care about. You can find what package a file is installed by with dpkg -S /path/to/file and get a description of the package with apt show packagename... so you can pick through packages to see what they do before you remove them.

A number of issues with killing random stuff that you don't know what it is...

Each process running is doing something. If you kill it, whatever that something is won't be working anymore. So before you start killing random things, you should find out what they are doing and what service they are providing.

Many processes are started by and monitored by sytsemd, so if you kill them, systemd will just restart them. So killing them might not just disrupt what they are doing, but it might be useless as they might be restarted.

You specifically ask about snapd. No, snapd is not just used to install snap files. It maintains the snap environment, so all snap based software would malfunction if you killed snapd. If you want to find out if you really need it, run snap list to find out what snaps you have installed. If you don't need any of them, you could probably uninstall snapd. (apt remove snapd)

You say that you have multiple 'python' processes. This doesn't really say much, because python is an interpreter, so the real program running is a python program whose name you haven't mentioned.

A number of issues with killing random stuff that you don't know what it is...

Each process running is doing something. If you kill it, whatever that something is won't be working anymore. So before you start killing random things, you should find out what they are doing and what service they are providing.

Many processes are started by and monitored by sytsemd, so if you kill them, systemd will just restart them. So killing them might not just disrupt what they are doing, but it might be useless as they might be restarted.

You specifically ask about snapd. No, snapd is not just used to install snap files. It maintains the snap environment, so all snap based software would malfunction if you killed snapd. If you want to find out if you really need it, run snap list to find out what snaps you have installed. If you don't need any of them, you could probably uninstall snapd. (apt remove snapd)

You say that you have multiple 'python' processes. This doesn't really say much, because python is an interpreter, so the real program running is a python program whose name you haven't mentioned. Many parts of linux are written in python, so killing those could cause many problems.

Rather than killing random processes you found, a better approach to sliming down your system would be to start by looking at what services systemd is starting using systemctl list-unit-files and browse through the enabled services and determine what each one does. For instance, the command systemctl status apache2.service would tell you if that service is running, and the Docs: line has a link you can look at if you don't know what that service is. If you decide you don't want a service, you can temporarily stop it with systemctl stop ... or permanently with systemctl disable --now ...

You could also outright remove software you don't need with apt remove... but you should also carefully read what else gets removed before you tell it to go ahead and do it to make sure you are not doing something silly like removing your entire graphical interface software suite or something else you care about. You can find what package a file is installed by with dpkg -S /path/to/file and get a description of the package with apt show packagename... so you can pick through packages to see what they do before you remove them.