OK, after playing up to the start of the Fall segment where Joel and Ellie are approaching Tommy's Dam on a new Hard mode run, I have checked visuals up close on many wall surfaces, but I also found I was not all the way updated to the latest patch version. I can now run it on FSR 2 at Quality mode and get at or near 60 FPS most of the time. It has even sped up Joel's run and reaction time, and the shaders compile in about 15 min now, quite an improvement (I purposely deleted the cache folder just to check shader compilation again on the latest patch)..
I focused a lot on inspecting brick walls, since that was one of Digital Foundry's main nit picks. I never saw any brick walls as blurry as they show in their video, but it's painted flat wall surface's often DO look a bit blurry. So I have to wonder if Digital Foundry made that video on a prior patch version. They pretty much warn viewers at the start of the vid that they've heard talk of new updates coming on a regular basis.
To be clear, I don't like the VRAM or RAM requirements for 1440p or higher AT ALL, or the game's tendency to use so much CPU, but when it comes to playing on older spec at 1080p, the game can definitely handle it. In fact I went back to bumping up AF to 16x, and am now running High Characters Texture Quality, which still fits within my 8GB VRAM and shows no signs of worse performance.
However, the game now has this weird tendency to post a message on subsequent launches that last time it shut down abnormally, asking me if I want to launch it in safe mode and enable diagnostics, even though it shut down fine. I just say no to both and it launches, now quicker than before (no wait for spinning coin to appear). It does as well on rare occasion show a larger error reporting message, though not when shutting down. This could be the reason for the message that it shut down abnormally, but I just click no, it disappears, and it's as if nothing had happened.
So it seems clear the latest patches HAVE caused some weird false error messages or something, but actual in-game performance has improved quite a bit from what I've seen. I say false error messages because so far the game HAS NOT actually crashed to desktop once on this new run up to the start of the Tommy's Dam segment. I get the feeling the false messages are a problem with the diagnostic system they're using, but why it would generate false error messages when I have yet to actually enable the diagnostics when asked seems strange.