I don't think this is a Fusion problem. It's more likely a name resolution issue in the VM. Double check to see that DNS is configured properly in the guest.
What is the output of "dig google.com" in the VM? It may give us a clue as to which DNS servers are being used and how quickly they are responding. Also, what does "resolvectl status" say in the VM about the DNS servers that are in use?
One other thing to check - I have seen this happen to several Linux distros if the VM's hostname has been changed but /etc/hosts in the VM has an entry for 127.0.1.1 that does not match the hostname of the VM.
For Kali, check the hostname of your VM, and then make sure that it's in the /etc/hosts file. My VM's host is named 'kali' and here's what you see if you check things out in the VM:
If the hostname doesn't match the /etc/hosts entry, name resolution will be delayed.
- Paul (Technogeezer)
Editor of the Unofficial Fusion Companion Guides