I think you misunderstand my intention. I’ll attempt to elaborate.
The goal is not to run the AEP in order to run the script. That would, indeed, be backwards. I’m conceiving of a script that loads lots of pre-created elements for the user, into their own project. Rather than do a boatload of scripting to generate these elements, it would seem much easier to have an AEP full of these elements (like comps and such) that the script simply opens and imports. So the AEP is simply a resource file that the script needs. The script is kind of an import tool, invoked within whatever project the user is working on.
Which is why I’m trying to think of a logical and reliable place for the resource AEP to exist for the script to call upon it. It seemed logical to me that it reside along with the script itself, making “installation” simple, and to my human brain, seems like a place where it could be “found” fairly easily… if I could deduce where either the ScriptsUI folder is, or where AE is running.
Does that make more sense?