ANR may cause bad effect if configuration ANR is not good.
Firstly you should check worst cells hosr, worst relation A->B hosr.
Pci conflict, confusion may also.
What is the metric used for 4G_Intra_Rat_SucessRate calculation?
Verify what are the relations with more failures it will help you to identify reasons as PCI confusion, overshooting cells…
Bit weird for me in your graph we have HO_SR > 0% with no attempts on S1 before the feature activation.
Check Ho stats, if there is any unnecessary relation like 4th tier cells or overshooting cells remove that relations using targets tilts or block that relation.
As well as check our cells TA.
Try to disable ANR, delete Relation, Activate ANR again with this script: (it will give you fresh relation on your enodeB)
MOD ENODEBALGOSWITCH: AnrSwitch=IntraRatEventAnrSwitch-0&IntraRatAnrAutoDelSwitch-0;
MOD GLOBALPROCSWITCH: X2BasedUptNcellCfgSwitch=ADD_NCELL_CFG_SW-0&MOD_NCELL_CFG_SW-0&DEL_NCELL_CFG_SW-0&ADD_FREQ_CFG_SW-0;
MOD ENODEBALGOSWITCH: AnrSwitch=IntraRatEventAnrSwitch-1&IntraRatAnrAutoDelSwitch-1;
MOD GLOBALPROCSWITCH: X2BasedUptNcellCfgSwitch=ADD_NCELL_CFG_SW-1&MOD_NCELL_CFG_SW-1&DEL_NCELL_CFG_SW-1&ADD_FREQ_CFG_SW-1;
rogue eNodeB uses legitimate mobile devices as a covert channel to launch attacks against SON enabled LTE networks.
this cause X2 signaling flood when more cells are impersonated