The usual recommendation is to NOT keep the screen alive because it drains the battery, so instead activate it when needed and run a background service to keep the app running. I am in the same boat as you, needing a watch app to stay running, and it seems reasonable to keep it on-screen to make it work during development. That way you can see whether it's doing what you want, and later bury it in the background.
On the Android side of life, I found this Java:
android.view.WindowManager; <<< which pairs with:
getWindow().addFlags(WindowManager.LayoutParams.FLAG_KEEP_SCREEN_ON); <<< after setting the content view.
I don't know whether the same function exists in a B4A library, or whether google still supports it. (book was published 2015)
On my LG G watch, it keeps the current screen on while it's being charged, while the screen flips off immediately when I wear it and drop my hand.
It will be interesting to see if I can over-ride this behaviour.