The initial approach for manual Dependency Injection (DI) involves using FindObjectsByType<MonoBehaviour>() on every scene load to inject dependencies into interactable objects. This method presents scalability concerns due to potential performance bottlenecks in larger scenes. Furthermore, dynamically instantiated MonoBehaviour objects at runtime do not automatically receive dependencies, necessitating an additional mechanism to ensure proper wiring.

To optimize your architecture:

1. Create a CompositionRoot with a DefaultExecutionOrder of -100 to ensure it initializes before other scripts.
2. Define an interface-based system where components like your interactor script implement a common interface.
3. Use a Factory pattern for runtime objects, where the CompositionRoot provides dependencies to the factory.
4. Subscribe to SceneManager.sceneLoaded to manage dependency wiring during additive scene loading.

Additional Tips

• Use FindObjectsSortMode.None when calling FindObjectsByType to avoid unnecessary sorting overhead.
• Transition from scene scanning to explicit registration for high-performance requirements.
• Implement a global CompositionRoot for persistent services and local roots for scene-specific logic.