It is needed for seamless 802.11r roaming. Above advice would lead to poor multi AP experience with MikroTik.
According to the docs, roaming is possible only between APs that are managed via the same RouterOS instance (own wifi interfaces of the instance, plus CAPs managed by CAPsMAN from this instance):
For a client device to successfully roam between 2 APs, the APs need to be managed by the same instance of RouterOS. For information on how to centrally manage multiple APs, see CAPsMAN
I have setup hAP ax³ as CAPsMAN and AP, and hAP ac³ as AP. The 802.11r/k/v/ roaming works perfectly since I setup CAPsMAN (well, for some Android devices, WPA3 must be disabled - I mentioned it here previously). Now, I’ve added hAP ax² to the setup, and roaming works great between all three.
Without CAPsMAN, it would be very noticeable. Literally tens of seconds of poor connection barely transmitting few bytes,… before the client, and if ever by itself, “roams” (re-connects) to the closer AP / the one with better signal in current location.
The roaming did not work at all without CAPsMAN, and I had to manually re-connect (or turn off and on wifi on the client), when I moved to closer AP, even if literally standing 1m from the closest AP and the current connection was still hanging on AP behind 1 wall, 2 floors, and very weak signal.