“Android” doesn’t doesn’t have any relevance when it comes to display support.
The display negotiates its settings with the kernel by sending it a packet of data called an EDID. The kernel checks this EDID and if it is able to provide a display mode compatible with the monitor, then the monitor comes alive. This all happens BEFORE Android starts up.
Similarly, the touchscreen digitizer is also something between the hardware and the kernel. Virtually ALL USB touchscreen digitizers now work with Linux.
The biggest stumbling block that you can come across in picking a display for these units is in the clock generator on the board’s SoC. It is not quite able to reproduce the timings necessary for standard HDMI modes. Monitors that are extremely rigid about the modes they accept may refuse to light up. But again, this has absolutely nothing to do with Android, rather it is a hardware limitation.
I’d be willing to wager $50 that the monitor you link to WILL work on this board. Reason being that I can see in the pictures of the display controller board, that it is a realtek chip, which is a particularly common chip used in small displays (its the same chip used in the second of the two monitors I linked to), and they all run variations on the same software.