You have to implement post clone operations of ps schema as hooks of the vdb "at config time".
This way once the vdb is created the hooks will fire up and change the schema to sweet the non-prod application server. (Meaning the app team will have no work to do just go and connect).
People soft application has meta-data info and a table with login credentials in the PS schema. Now that PS schema has suffix P in prod and suffix D/T/A in LE how do we implement it? if we have script to preserve the metadata tables it will go into suffix D/T/A will that work as the PS schema is coming from prod which has suffix P.
This a 100% oracle operations and delphix has nothing to do with it.
So the idea is to rename the PS schemas to switch the environment, I can perpose 2 way do achieve your need :
1- do export / import with schema remap (this is a full schema export/import)
2- you can use export / import with exporting only tablespace metadata and reasign the tablespace data file to the new schema (e.g. https://www.google.fr/amp/s/pierrefor...
The easiest way I found is :
a) create schema with good prefix on new vdb
b) fill it with synonyms pointing to tables with production prefix (to avoid doing exp/imp)
And try every feature delphix and vdbs can provide you with.
If your are happy with product you should work on the question of schema with prefix do you need to have as prerequisite or avoid it to ease cloning ops.
The app layer is already customized for that particular database, so only a post sql script (we call it a hook) needs to be issued, to customize the data content, after the data refresh completes. You already have that script created so you can just place the code in our hook operation.