A fair reaction - particularly given that Funcom has not named the third party (though there may be contractual obligations impacting that). However - decay timers changing is something that happens regularly, without incident. Hypothetically, what could have happened is that a change made by the third party had a knock-on effect that then triggered the actual conflict when the decay timers were changed in the normal way, suddenly revealing the impact of the actual change. This would explain the timing, while also fitting the evidence.
My personal suspicion, given that this has only impacted XBox and not PS (or Epic), is that maybe Microsoft made some small base level change to XBox that then interacted badly with some element that Funcom had made years ago to work around something. Others have theorised Playfab (a Microsoft subsidiuary used to do with FLS) may have made a change with similar consequences. Of course this is all speculation, but given that only XBox is affected, it certainly suggests something unique to XBox. Of course, there are likely some elements of Funcom code unique to each platform from the porting process (but as I understand it, porting is also carried out by third-parties, so…), so it could be something to do with that - but I would have thought any such issue would have arisen closer to when actual substantive changes were made, rather than merely a ‘button press’ like decay timers.