Anyways, to any poor soul who finds themselves in this mind numbing situation, the way i booted back and fixed this, was by: (keep in mind there might be a better way to do this, this is just the way i did it)
First i tried to boot into a snapshot in GRUB, use the snapshot which you last remember working, and note its number, if you manage to boot, just restore it, otherwise continue below.
First i booted into i live Garuda Linux USB and opened up the terminal, in the terminal i issued:
mkdir /mnt/restore after which i issued sudo mount /def/sd[x] /mnt/restore (where [x] without the parentheses stands for the partition number, mine was sda2, yours might be different, just use lsblk to find the biggest drive and, mount that)
After mounting the partition changed dir to /mnt/restore with cd /mnt/restore.
After changing your dir and listing everything with ls, you should see a bunch of directories with the prefix @.
First check if the kernel is present, issue command ls @/boot/ if you see files that have a name vmlinuz-linux-zen then the kernel is there. It it isn't there do the steps below, also do it if you aren't sure that the kernel isn't corrupted.
If you want to be sure then you can unmount /mnt/restore with sudo umount /mnt/restore and open up Garuda Assistant, and click chroot, wait until you get into the shell and then issue
sudo pacman -Suy linux this should reinstall the linux kernel. Try to reboot. If you manage ro boot then great! Otherwise continue with the steps blow
Mount your partion back with sudo mount /dev/sd(x) /mnt/restore, and issue cd /mnt/restore/@/.snapshots after which issue btrfs property set -ts [snapshot number]/snapshot ro false after that, reboot.
Now try to boot back into the snapshot, after that, restore. Reboot again, this time normally, and do a full system update with the Garuda Assistant or in the therminal with sudo pacman -Syu.
Good luck! 