For minimOSD you just have to compile mwOSD with dRonin support (dRonin can make it do with the regular betaflight-mwosd firmware, but you end up with plenty of useless screens), from then on, in the GCS, you enable MSP protocol on one of your UART and connect this uart TX/RX to minimOSD.
Note that Once MWOSD is properly flashed you can use the flight controller as and FTDI adapter in order to setup MWOSD! For this you disable the MSP protocol and enable the com-bridge instead (second drop down of the USB port and UART port have to be defined as "bridged"). Once the flight controller is connected through usb you will see an additional comport in windows, this will be the comport to be used with your mwosd configurator.
The built-in OSD is obviously better than a separate MWOSD. I do not know how the graphical chip is connected to the AQ32 board, so no idea whether dRonin can actually use it in order to run the buit-in OSD. Obviously there are some UAVObjects related to the OSD on the AQ32 (https://github.com/d-ronin/dRonin/blob/3a866925d6148e33e0620c94c5940413574a7247/shared/uavobjectdefinition/hwaq32.xml), so with a bit of luck the OSD support is similar to the Omnibus boards... You could look at the hardware tab (in the GCS) and search for a drop down list with the MAX7456 chip?