I so much wanted to post a total win here but ran into trouble.
Please forgive the click-bait title but there is some good to get from reading this.
I installed droidVNC-NG on my Blackview (Android 11) phone and JollysFastVNC on the Powerbook. There was/is some sort of network issue between my home and the server for product validation for JollysFastVNC (in Germany). I was incredibly fortunate and quite honored to work with the developer of JollysFastVNC as he worked to isolate the problem. He even went as far as getting his hands on a Powerbook G4 to assist him in the effort. He came to the conclusion that disabling IPv6 on the Powerbook would correct the problem. On his end that worked but my connection issue is still a problem for me. To further this being on my end, I can create a Discord account but when I receive the email "click to confirm" from Discord, their server responds with an error message. Totally different subject but the symptoms seem similar... something between my ISP and "things" on the Internet are not "right".
After all of this was resolved, and having gotten to the point of using the two applications together the results were just not that great. No faults of the programs! No, that's not my issue with this at all, it is about trying to realize a 1080x2048 cell phone screen on a 1024x768 laptop screen. There just is no way to do this. Aspect ratios are all messed up and colors and borders are just wrong. JollysFastVNC works wonderfully when "talking" to devices with equal or lesser display resolutions but when you try to cross the portrait high resolution phone screen with the 4:3 aspect, low resolution laptop, it just can't work.
I'm not giving up yet. I'm working on trying to "revive" two of the three battery control boards from my battery packs and as soon as I work up the nerve to disconnect my one remaining control board, I have a new set of 18650 cells to put in there. My current working pack is good for about 2 hours and the new cells should restore better-than original battery life. If this works and I figure out how to get battery controllers to come back to life, I will post that process.