I have all three version slots installed for both, and my /boot usage is below 600 MiB. But it depends on the size of the initramfs generated during kernel updates. They can be larger if more kernel modules happen to be loaded at that time, or I guess if more firmware blobs need to be bundled, or if dracut was configured for no-hostonly mode.
Anyway yes it would be better if the installer defaulted to 2 GiB for /boot.
qubesos@dom@:\~$ sudo grub2-mkconfig -o /boot/grub2/grub.cfg
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-7.1.6-1.qubes.fc41.x86_64
Found initrd image: /boot/initramfs-7.1.6-1.qubes.fc41.x86_64.img
fgrep: warning: fgrep is obsolescent; using grep -F
Found linux image: /boot/vmlinuz-7.0.14-1.qubes.fc41.x86_64
Found initrd image: /boot/initramfs-7.0.14-1.qubes.fc41.x86_64.img
fgrep: warning: fgrep is obsolescent; using grep -F
Found linux image: /boot/vmlinuz-7.0.12-1.qubes.fc41.x86_64
fgrep: warning: fgrep is obsolescent; using grep -F
Found linux image: /boot/vmlinuz-6.18.42-1.qubes.fc41.x86_64
fgrep: warning: fgrep is obsolescent; using grep -F
Found linux image: /boot/vmlinuz-6.18.40-1.qubes.fc41.x86_64
Found initrd image: /boot/initramfs-6.18.40-1.qubes.fc41.x86_64.img
fgrep: warning: fgrep is obsolescent; using grep -F
Found linux image: /boot/vmlinuz-6.18.35-1.qubes.fc41.x86_64
fgrep: warning: fgrep is obsolescent; using grep -F
fgrep: warning: fgrep is obsolescent; using grep -F
Adding boot menu entry for UEFI Firmware Settings
done
Wanted to flag that the instructions might be incomplete and lead to data loss when writes fail as qubes_dom0/root appears backed by qubes_dom0/root-pool. Accordingly, the root-pool also needs to be enlarged. Otherwise, writes may start to fail when the root-pool size limit is reached.