https://www.hadouken-arcade.com/product/pre-order-vewlix-universal-monitor-bracket-batch-2
Oh, universal mounting, so convenient. ^^
If I knew the information you provided me, I would have looked for a monitor with G-Sync and a more powerful PC, so I could do Frame Delay 9,
If you have a G-Sync or FreeSync setup you don't need Frame Delay!

Groovy produces no lag when in 'hands off' mode as I like to call it, that is when autosync (and any other sync option if you have to make sure) is turned off, which is what is required for Gsync or Freesync to work as intended.
Baseline MAME received the same ability recently wih the 'low latency' option (which means what I just explained: no lag when using a VRR setup), thanks to Calamity again.
Playing in VRR also doesn't spend any extra CPU/GPU resources, unlike frame delay.
Emudrivers and Frame Delay on LCD/flatpanels are meant for setups not officially supporting VRR like gsync or freesync, but still able to do something similar under certain conditions (like again some ViewSonic monitors and a unknown number of others on Earth), it is a very niche case scenario, more complex to set up than just firing Gsync/Freesync...it is a bit tricky 'home-made VRR' for
free.

(Calamity called that 'bleeding edge old tech' iirc)
but as it is, the emulation seems pretty good with Frame Delay 4-5 with no screen tearing (or I can't see any).
Yeah even modest frame_delay levels can make gameplay feel very responsive.
The matter of tearing though...
[rant extension warning] well, it's always a stressful question. I can't tell anything without seeing your full configuration (generated log & mame.ini), and even if you showed both I'm not really the best person here to spot every possible issue that would be obvious to the handful of power-most users around, but in general when users in a LCD case scenario say "I can't see any tearing" I always can't help but first suspect something is wrong.
Why? because I have built a lot of experience using Groovy on flat panels so I'm kinda used to how the beast behaves in that particular niche area of use. Most Groovy users you'll meet, save for Calamity himself, only experienced on CRT 99% of the time. Rules for flat panel displays are in large parts similar but the forces weighing on the system definitely not the same league.
-There can be situations where a manner of vsync superseding Groovy's is forced over (misconfiguration, sync forced by OS in windowed or non-exclusive fullscreen), in which case the features intended by Groovy are not actually working.
-Or the settings are right and the intended autosync behaviour active, but the CPU+GPU combo powerful-enough and the monitor's resolution low-enough, like for instance a 720p TV instead of a 1440p monitor (= factors that matter a ton more than with CRTs), so that the tearing line is there but very small and you won't notice it, even less over HLSL with simulated scanlines that might hide the tear line,
or not at all in a scrolling-less game (like Tetris) where vsync doesn't matter much.
-Another quite revealing case of smth being wrong is when people say they can easily push frame delay to 9 in every game (which btw isn't desirable because often counter-productive for lag), it either means Groovy is not working at all, or that they have stolen a supercomputer from NASA.
-Many casual users don't get the meaning of
autosync and
sync_refresh_tolerance relationship, and how important that is for the effectiveness of frame_delay. The default settings in Groovy make the main features like smooth sync and frame_delay work only for games that are natively between 58Hz and 62Hz, outside of that range a triplebuffer is used and neither smooth sync nor lag reduction will work anymore. You are not concerned with TGM games bu that's just another case to illustrate.
-etc yada yada
[end of rant extension] 
My advice if you don't mind unreasonable spending: get a Gsync of FreeSync setup: it is accuracy and laglessness
without hassle.
It is a big expense if
just for TGM2/P, but heh, a stronger CPU/GPU for getting higher frame_delay is expensive too. Pick your poison.
Note: beware of 4K monitors (or of any other resolution) that support gsync/freesync BUT are capped to 60Hz. Just avoid those, you want VRR that goes beyond 60Hz, like 75Hz at minimum, it is mandatory for 61+Hz games like TGM2/p.
I haven't looked into 32" options in a long time so I can't recommend models right now.
Realistically I am probably the only one around here or anywhere else using a fully-featured Groovy+Emudriver LCD setup, it's awesome and accuracy-wise wipes the floor with any other MAME build or other arcades emulator (don't even mention RetroArch), as long as gsync/freesync are not options, which was my situation.
But this unconventional 'path' currently is still only meant for
power users who don't own/want to pay for fancy nVidia nor AMD techs.
Come back maybe in 2021 if you want a more user-friendly version of GroovyMAME that is AFAIK in development, and should make using LCDs/flatpanles much easier.
Yes, I take my Tetris seriously! 
