The Mac does not require or use any installable drive for monitors, you literally plug it in and it works.
Probably if you only had the LG screen connected and not also the HP you may never have noticed this issue. The way the Mac knows what resolution and capabilities the monitor is/has is the Mac like all computers reads information sent by the monitor down the cable. This information is called 'EDID' Extended Display Identification Data.
Sadly and amazingly many monitors and TVs have errors or omissions in this data. Most of the time this does not cause serious issues but this is probably the cause of what you are seeing. At a guess either it is sending the wrong size value but the correct number of pixels, or it is sending the wrong dpi figure i.e. how big each pixel is.
Now whilst I said that the Mac does not require or use any installable driver for monitors and this is true, the Mac does come with some settings files for known monitors, these are stored in the following location.
/System/Library/Displays/Contents/Resources/Overrides
It is potentially possible to add a custom override although to do this you may need to disable the SIP protection that more recent versions of OS X have included. See About System Integrity Protection on your Mac - Apple Support
You can dump the EDID data on the Mac in a variety of ways but one of the simplest is the following command in Terminal.app
ioreg -lw0 | grep "IODisplayEDID"
The actual EDID data is in between the < > symbols. It maybe easiest to do this with just the LG connected only. In theory this website can decode this to a more human readable form. See http://www.edidreader.com/
However I found better results using the free edid-decode tool. You could download the source code for this and compile it, I am struggling to find a pre-compiled version for the Mac although it does work on the Mac. However another Mac tool called Darwin Dumper includes a copy of edid-decode and Darwin Dumper is available here https://bitbucket.org/blackosx/darwindumper/downloads/ Darwin Dumper can also get the EDID date for you without you needing to use Terminal.app
One approach would then be to modify the EDID data to correct the problem and 'flash' the ROM in the display, however for most people this is not going to be practical. However you could use the information to generate a monitor override file as mentioned above. A tool called FixEDID may help here. A zip with both source and a Mac binary is available here http://mac.softpedia.com/get/Utilities/FixEDID.shtml you need to use the EDID output produced using Darwin Dumper. I believe Darwin Dumper can product, Text, Hex, and Binary versions and FixEDID needs the binary version.
Basically you produce an override file which matches the Monitor identification but also contains settings to override the settings the monitor has sent.
The actual changes are beyond my level of knowledge and would be specific to your monitor.