That's because FxESR 52 gets by default the (supported) Polymer v1 (Pm1) layout; only versions of Firefox older than 44 (Fx <=43) are being served the Classic layout, the one to be retired in March; if you use a UAO on FxESR 52 to spoof it as Fx 43, you'll get the older layout with the deprecation infobar:
BTW, Firefox (Quantum) versions newer than 62 (63 =< Fx) are being served the newer Polymer v2 (Pm2) layout, which, on the outside, looks a lot like Pm1, but on the inside it's quite a different beast... FxESR 52 and the UXP browsers don't currently support it; of course FxESR 52 isn't maintained anymore, but MCP devs are already making talk about "upgrading" UXP to support Pm2 in the coming months; Google have not yet indicated for how long they'll keep supporting Pm1
Pm1 is considerably more resource hungry compared to the out-going Classic style, and this fact alone will create problems for older browsers capable of handling Pm1 but which are installed on old hardware (which seems to be the case with many XP/Vista users here... )
Of course, the forced migration to Pm1 will disable many user YT customisations, in the forms of XUL extensions, userstyles, userscripts etc., which were initially targeting the Classic layout; sadly, it'll be game over for those older browsers (on, perhaps, even older OSes/hardware) that can't cope with Pm1 at all...
Some relevant links:
https://support.google.com/youtube/thread/27596769
https://www.reddit.com/r/youtube/comments/eyjy4i/misc_fd_youtube_is_removing_the_old_design_soon/
https://forum.palemoon.org/viewtopic.php?f=3&t=23566
Chrome 49 has adequate support for Pm1, so if OP wants to continue using it for YT past March 2020, OP must:
Install the User Agent Switcher extension from GWS:
https://chrome.google.com/webstore/detail/user-agent-switcher/kchfmpdcejfkipopnolndinkeoipnoia
Set a "Permanent Spoof" for youtube.com domain (aka SSUAO) and pretend to be Firefox 60 (e.g. Mozilla/5.0 (Windows NT 6.3; rv:60.0) Gecko/20100101 Firefox/60.0); then, every time a YT URL is loaded, OP will get the supported Pm1 layout without any nags about an unsupported browser:
However, that workaround will, sadly, come to an end when evil Google decide to remove Pm1, too (which can be anytime, I hazard a guess and predict some time towards the end of this year) .