Hello:
FYI: The FSX.Cfg file parameter 
TEXTURE_MAX_LOAD  must be distinguished from 
TextureMaxLoad.
Texture_Max_Load is the maximum texture resolution in pixels allowed to be displayed by the FS run time rendering engine.
TEXTURE_MAX_LOAD=4098 means FX is allowed to display textures up to 
4096x4096.
FSX returns this value to the 
default 1024 every time it is re-loaded unless it is automatically restored by a 3rd party utility
TextureMaxLoad works in conjunction with 'TEXTURE_BANDWIDTH_MULTIPLIER' and is related to how FSX loads textures; reportedly changing this value correctly results in improving the blurries or stutters at run time.
https://www.avsim.com/forums/topic/400862-fsxcfg-texture_max_load-vs-texturemaxload/
https://www.avsim.com/forums/topic/281312-texturemaxload-vs-texture_max_load/
I agree that one should set TEXTUREMAXLOAD=4096 to enable display of mapped texture image materials at max resolution.
However, one should also be certain to inspect all mapped textures in 
ex: SDK ImageTool to ensure that all such mapped texture images have between 7 to 9 MIPMAPs depending on the FS object type to which they are mapped as Materials.
Otherwise one may find that the FS rendering engine will attempt to create such a lower resolution MIPMAP compatible with the current local context of Texel Density for the LOD level being displayed, and IIUC, such MIPMAPs created 'on the fly' at run time may not appear to be as visually 'sharp' as a discrete MIPMAP loaded from within the texture image that were created 
ex: SDK ImageTool.
Additionally, there may a cumulative adverse performance impact if rendering many local objects that do 
not have MIPMAPs.
https://www.google.com/search?ei=zBNOW7T_GMq-jwTfmbvYBQ&q=site:www.fsdeveloper.com+MIPMAP&oq=site:www.fsdeveloper.com+MIPMAP&gs_l=psy-ab.3...998721.1003983.0.1007408.13.13.0.0.0.0.224.1188.9j2j1.12.0....0...1c.1.64.psy-ab..1.4.552...0j0i67k1j0i131k1.0.Hb2E4dQV4go
GaryGB