Sure, but that requires working around all sorts of weird bugs and issues VirtualBox has; performance issues are far from the only one. For instance, the NVMe devices in VirtualBox report a completely wrong value for “max_transfer_size”; all transfers above ~700KB or so fail, while it reports 2MB as the “real” limit, which makes NVMe I/O under VirtualBox extremely unstable.
Whatever the problem is, is almost certainly VirtualBox’s fault, and so I don’t have much interest in investigating. Someone else could, of course.
It claims to be free and open source, but last I heard, the provided source tarballs were insufficient to actually build a working Windows version of VirtualBox; there were missing files or something like that. But maybe this has changed recently.
Additionally, QEMU now supports using the Windows Hypervisor Platform (WHPX), so if you enable that (on Windows 10) and pass the right command line argument, QEMU will be hardware-accelerated under Windows. So, no, VirtualBox is not the only option, either.