Does not compute.
We can see from the very useful screen shot that this message originates from the Now(TV) app, which could hardly be too slow for itself 😛
But it could still be that the Now app is too hairtrigger, too quick to decide that the TV can’t do HDCP 2.2, whereas perhaps before the latest update it gave the TV longer to respond?
The common factor in both cases is that this is an interaction between the Now app and the TV.
it’s not an HDMI cable issue, not with any HDMI cable supplied with the device Now is running on anyway, and it’s not a platform issue, e.g. Amazon Fire device versus Now/Roku device.