After Effects MFR serializes full composition with legacy plugins

Multi-Frame Rendering Plugin Compatibility Diagnosis

After Effects 22.0+ renders multiple frames concurrently through Multi-Frame Rendering (MFR). When a legacy plugin without explicit MFR support is applied, the composition falls back to single-frame rendering for the entire project rather than isolating the affected layer.

The goal is to determine whether Adobe provides any mechanism for plugins to declare selective thread-safety at the callback level, or whether developers must accept all-or-nothing serialization. No public manifest flag or runtime query distinguishes MFR worker processes from the main UI process, and MFR spawns duplicate renderer processes that each load full project state.

Memory pressure can occur when plugins allocate large GPU or CPU buffers per renderer instance, especially on systems below 32 GB RAM. Adobe's troubleshooting guidance covers global MFR disablement but lacks diagnostic logging to identify the offending plugin.

Has Adobe introduced any post-v22.0 SDK mechanism for partial thread-safety declaration? Is there a per-effect or per-callback serialization workaround that avoids disabling MFR globally? What diagnostic methods can identify which plugin triggers full composition fallback?