What you are describing sounds like an anti-pattern in your application design - and specifically a usage that is not supported or recommended. As others have said, it is hard to determine exactly what you intend, but all information you have provided above points to an anti-pattern.
Client devices should ONLY need to have the Trusted Root, such as ISRG X1, installed. This should be handled by the Operating System or an Application's sandboxed trust store. Clients should not need Intermediates installed - those should be installed on your Server and provided to your Clients as part of the https protocol.
Servers should have the Trusted Root and Intermediates installed as their Chain/FullChain configuration, and the EndEntity (aka Leaf or Client) Certificate installed as their active certificate.
Beyond that, the ACME protocol is explicitly designed to issue Certificates alongside their Full Trust Chain, and the RFC explicitly states that Intermediates and Trust chains should not be hard-coded into clients, and that clients must expect these to change at any time.
While it is possible that your devices required a new R3 certificate to be installed, it is almost guaranteed this is because of a bug or architectural mistake in your application design. Attempting to work around these behaviors will only assume more technical debt, not solve your actual problems in any meaningful way.