A little tough to tell what happened without information on the current disk setup. Did you install using manual mode, or did you choose an automated install?
Stuff we might need includes the output of lsblk and perhaps inxi -Faz. Copy the output from the terminal CtrlShiftC - add 3 `, then paste into a message, and follow the paste with another 3 1 (for each of the items). Once we see that we might be able to guess what’s going on, and possibly clean it up…
but instead, this is generated by debian based version of grub:
initrd /boot/intel-ucode.img
The easiest solution is to use EndeavourOS grub but if you want to continue using your existing version of grub, you will need to edit the “initrd” line of all “menuentry” s for Arch based systems.
Alternatively, you could disable or uninstall os-prober and manually create the entries for your Arch based systems in /etc/default/grub.d/40_custom
The ISO is not using grub at all, it boots on systemd-boot if EFI and syslinux if Bios-legacy…
As long as user do not start anything or run any command the LiveISO is not doing anything to the system.
But it is possible that usermuck up his system. as you can do almost everything from the live session… like deleting partitions or removing folders, overwriting.