This issue has been added to the list of things to be looked at, but with only two reports, it's still kind of chilling at the bottom of that list. It will take more folks reporting it to bump it up the priority list, as there are other issues that have more of an impact on more users, currently.

If it were me, I'd investigate ways to avoid using two plugins that both use guzzlehttp in the meantime.

I wish we could justify dropping more urgent issues to fix this sooner, but we've got limited development capacity and have to weigh tradeoffs.