Maybe you can use a generator method somewhere in your code to create the WebApp, something like:

ClassMethod CreateApplication() As %Status [ CodeMode = objectgenerator ]
{
Set $ZTrap="Error"
New $Namespace
Write !,"Creating XXX API",!
Set URL="/xxx"
Set $Namespace="%SYS"
If ##class(Security.Applications).Exists(URL) {
Return $$$OK
}
Set Props("Name")=URL
Set Props("NameSpace")="%SYS"
Set Props("Description")="XXX API endpoint"
Set Props("AutheEnabled")=64 ; unauthenticated
Set Props("DispatchClass")="API.Handler.Class"
Set Props("Type")=2 ; CSP App
Set Props("MatchRoles")=":%All"
Set sc=##class(Security.Applications).Create(URL,.Props)
Return sc
Error
Set $ZTrap=""
Return $$$ERROR($$$GeneralError,"ErrorTrap: "_$ZError)
}

I've trained about a dozen junior to senior developers in InterSystems (and predecessors) technology.
ObjectScript is the least you should worry about. Any developer who can't grasp that isn't worth hiring.
It's the IRIS ecosystem that is completely different from 'traditional' development. Globals, Namespaces, (Remote) Databases, Mirrors, Productions, Jobs. All concepts that are not found outside the InterSystems (MUMPS) realm.
If people get their head around that, they either love it or hate it.