Yep, the AVR definitely adds some data.
Yes - the AVR has to add the audio formats it adds support for in an additional EDID block (so that sources know that the AVR+Display sink combo now supports True HD, DTS HD MA etc. and not just the audio formats the TV supports). It can also add data with the AVR name.
A common problem with early '4K' compatible AVRs is that they only support the low (HDMI 1.4-compatble) bandwidth 2160p50/60 modes with 4:2:0 (which the Pi can't support) OR you have to enabled 'Enhanced HDMI 4:2:2' or similar to allow the high bandwidth modes to be added.
AIUI some AVR+TV combos will remove formats the TV supports but that the AVR can't pass through from EDID in this situation.
Also worth knowing that some TVs will go into 'PC' mode when they detect RGB rather than YCbCr (aka YUV - if you are happy to use UV incorrectly ) sources - as most consumer equipment is YCbCr output, and most PCs are RGB output.
I think you should try that. We have reports on the forum that different HDMI ports act differently. Usually the first HDMI port of the TV is the most capable one.
NB this isn't the case with a lot of Sony displays - particularly those in the early era of HDR UHD and Dolby Vision UHD support.
On 4 HDMI input Sony models from that era (My XE/XF 9000 series for example), HDMI 1 and 4 are often low bandwidth (so only support 4:2:0 at 2160p50/60 which the Pi doesn't) with HDMI 2 and 3 having full-bandwidth support for 12-bit 4:2:2 at 2160p50/60. One of these is the ARC port which is the port you'd always use for an AVR (so you get TV->AVR audio back to the AVR via ARC)
(4:2:0 2160p50/60 - at least at 8-bit - was added to the HDMI 2.0 specs as it was backwards compatible with HDMI 1.4 bandwidth connections so allowed old HDMI 1.4 physical hardware to carry 2160p50/60 video... )