Why doesn't UXP expose a direct evalScript-like API to run existing ExtendScript (.jsx) files?

I am reaching out to understand why UXP (the new plugin framework) does not expose a direct API to trigger and run existing ExtendScript (.jsx) files. In CEP (Common Extensibility Platform), we had the ability to use evalScript to run ExtendScript code within the same workflow. This offered immense flexibility and allowed us to leverage the full power of Photoshop scripting alongside UXP’s new features. However, with UXP, this functionality seems to be completely missing, and I am left wondering:

1. Why doesn't UXP allow us to run legacy .jsx scripts directly from the plugin?

2. Why isn’t there an official way to trigger scripts that are already installed in Photoshop (e.g., in the Scripts folder) via UXP?

3. Is there a specific limitation or future roadmap that prevents UXP from including a function like evalScript?

4. The ability to run scripts and control Photoshop deeply was one of the core strengths of CEP. By removing this functionality, we’ve lost a lot of power in terms of automation, scripting, and control. Why has this shift happened?

It feels like UXP is limiting creative professionals and developers by restricting this functionality. I strongly believe that reintroducing a similar flexible, scriptable interface would greatly benefit all developers building in the Photoshop ecosystem.