This has my interest. Many years ago many hobbyist were involved in interpretive languages, because you could easily invent your own syntax rules and have something easier to use that doing everything in assembly.
There wee two ways there were used. An interactive language that allowed an advanced user to make a change 'on the fly' and run the modified program. Or a 'hidden' program where it was very hard for the user to modify the script. The big advantage was the speed and correctness of development. You could modify and test a program dozens of times while another person was still waiting for the linker.
You can very easily put your script into the EXE of PB, or any similar language. You stay inside the rules of the implementation. The implementation rules for the EXE means that the EXE already has to have sits size defined at compile time, or the it must invoke another EXE as a child. The second EXE file can later be modified, withing limits, and can serve as aback door to updating or replacing the script. Or make DLL files if you like. PB can load DLL files, but it does not have to. Only if you want it to load some of them. This is in the documentation. Hiding a script in a DLL is a simple task.
You can do it.
There are few here that want to talk about Power Basic. It is a very vertical product presently, but at one time when it was Turbo Basic, it was very widely used. Got to the PB site and look around. Lots of stuff there.
Hint: PB and similar tools allow in-line assembler. You can do a short thing the does an XOR on a block of memory, flipping bits and making it unreadable for the average hacker. At run time reverse the process. Simple, quick and transparent to almost anybody.
Who's Afraid Of A DLL?
