As the man page states, it's game over.
Removing the last passphrase makes the LUKS container permanently
inaccessible.
That is, if you really removed the last key. Does cryptsetup luksDump show DISABLED for all key slots?
Normally cryptsetup prevents you from doing that, or at least asks for confirmation:
# cryptsetup luksRemoveKey foobar
Enter passphrase to be deleted:
WARNING!
========
This is the last keyslot. Device will become unusable after purging this key.
Are you sure? (Type uppercase yes): NO, ABSOLUTELY NOT OKAY!
It does that unless it's in batch mode or reads the passphrase from a pipe.
Personally I feel it should prevent you even then, after all if you really wanted to make it inaccessible you could just as well use luksErase directly. But that's not how it seems to work.
It would be a different story if you either had a backup of the LUKS header, or if the LUKS container was still open. The backup of the LUKS header you could just restore or use with luksOpen --header thebackup.header.
For an open LUKS container, you could obtain the master key with dmsetup table --showkeys and build a new LUKS header out of that as shown in this answer (it obtains the master key a different way but it's the same concept).