◇ Could this help me?
Yes. The explanation is technically accurate: animating layout-affecting properties forces layout and paint each frame while transform and opacity changes can be handled by the compositor, and the main-thread contention point is correctly described. This is worth internalizing because it turns a vague performance complaint into a specific rule about which properties are safe to animate. This is a general practice.
Review the animations in this project and list every one that animates a layout-affecting property such as position, width, height, top, or left. For each, rewrite it to use transform or opacity instead, keeping the visual result identical, and tell me any case where that substitution is not possible and why. Also flag any animation driven by script that could be expressed declaratively in the stylesheet instead.