Recently I have migrated my home WiFi from Ubiquiti to Mikrotik. During that migration I originally attempted to move the network entirely to WPA3-PSK. My Framework 16 would not successfully connect. Adding WPA2-PSK-SHA2 allowed the Framework 16 to connect. Since this worked on Ubiquiti and not Mikrotik, my guess would be it is a Mikrotik problem, but posting in both places just in case.
Laptop:
Framework 16, no GPU, Windows 11 updated to current
Having use a decent number of Mikrotik devices I know they have a long history of being very adaptable. Did you check it is running the latest version of their OS and Firmware on the router?
There is a console log that can be very exhaustive too for Mikrotik to see where the hangup might be.
I do not think I am running any of the newer WPA3 only modes on my devices. I might need to go see what is connecting and what is not.
Their hardware is crazy good for what it does and what it costs. I always have to remember that there are hardly any stops to prevent the user from misconfiguring as you can literally do anything you want on them. Winbox makes it really easy to poke around and see all the parts and bits available to them. Let us know if you find a solution!
It is looking more likely it is a misconfiguration by me on the Mikrotik switch. Not yet resolved, but during troubleshooting uncovered high packet loss. This ended up being a L2MTU mismatch between devices, and setting all to 9000 resolved that issue.