I’ve been in touch with support again, and they assured me that they haven’t forgotten about this and are still working on a solution, but that it’s turning out to be more difficult than expected.
They provided me with an older firmware version (from early 2025) on a trial basis, and I’m currently testing to see if the error occurs with it or not. Perhaps this can help in some way to identify the cause or find a solution.