Yes, editing the snapshot is only a temporary change. To make the change permanent, typically you'd have to use either Garuda boot options or edit /etc/default/grub and then sudu update-grub. On a broken system however, you have to do the latter two options from a live iso using chroot. The Garuda Boot Repair does this for you.
If removing it that way doesn't work and you still get the "you're on your own' message, can you post the output of lsblk -f, cat etc/fstab and ls -l / from within a chroot? The last one is to check whether your /bin and /sbin are symlinks as they should be, so the output should look something like this:
drwx------ - root 25 Mar 16:25 .config
drwxr-xr-x - root 23 Aug 01:59 .snapshots
lrwxrwxrwx 7 root 1 Feb 07:51 bin -> usr/bin
drwxr-xr-x - root 23 Aug 01:10 boot
drwxr-xr-x - root 23 Aug 23:44 dev
drwxr-xr-x - root 5 Aug 21:19 efi
drwxr-xr-x - root 23 Aug 01:49 etc
drwxr-xr-x - root 20 Mar 00:00 home
lrwxrwxrwx 7 root 1 Feb 07:51 lib -> usr/lib
lrwxrwxrwx 7 root 1 Feb 07:51 lib64 -> usr/lib
drwxr-xr-x - root 1 Feb 07:51 mnt
drwxr-xr-x - root 21 Jul 00:27 opt
dr-xr-xr-x - root 23 Aug 01:49 proc
drwxr-x--- - root 18 Aug 23:07 root
drwxr-xr-x - root 23 Aug 23:49 run
lrwxrwxrwx 7 root 1 Feb 07:51 sbin -> usr/bin
drwxr-xr-x - root 11 Mar 13:45 srv
dr-xr-xr-x - root 23 Aug 01:49 sys
drwxrwxrwt - root 24 Aug 07:54 tmp
drwxr-xr-x - root 23 Aug 01:06 usr
drwxr-xr-x - root 23 Aug 01:49 var
.rwxr--r-- 129k root 30 Mar 17:35 .face
.rw-r--r-- 7 root 11 Mar 13:47 .garuda-tools
(the unknown characters are folder icons)
Helpful links from searching the error
This is for further reading and also to see whether anything proposed here solves the issue 
Root device mounted successfully, but /sbin/init does not exist - Support - Manjaro Linux Forum
/sbin/init does not exist, systemd nowhere to be found - Support - Manjaro Linux Forum
Reddit - Dive into anything
^ init file nukes itself somehow
Fix Arch Linux boot issues | xpressrazor
^ Kernel command lines to try add