Here's a report on my experience. Let me start by saying that I think I added some confusion to the discussion as I was relating my experience with Kiosk mode while MattDPenn was working in managed guest mode. So, for example, anything I said about user properties and configurations was beside the point, as these don't appear to come into play at all given that the Guest account is the credential in use. I should have been working in the Devices tree instead of the Users tree in the console.
I grabbed a device, searched for its SN in the larger pool of comparable devices, and moved it into a new OU, configured according to https://support.google.com/chrome/a/answer/3017014?hl=en#zippy=%2Cstep-configure-your-chromeos-devic... . Then I set up the guest session according to https://support.google.com/chrome/a/answer/3273084?sjid=11250743825655956933-NC#zippy=%2Coption-scho...
Result: I can get everything but fullscreen mode. If there is a flag or argument or ampersand thinggy that can be added after the loop and slide change in xx ms values, I haven't been able to find it.
Of the two links above, the first one was useful in terms of distinguishing kiosk from guest user session and getting things configured along the Devices tree. The branch \\Devices\Chrome\Devices\ lands you in a dead end that looks like it's just a list. But it's only by back-tracking at that point by returning to \\Devices\Chrome\Settings where all the important stuff resides in the very long list of options (startup options, content in particular) where things really come together. I think this is my favorite Admin Console labyrynth so far. You can just picture the developer meetings and arguments over whether the long list of settings should be subheads under \Settings on the left or whether that would violate the current design standard for number of allowable subheads.
That second link regarding setting up assessments using managed guest sessions looks to be particularly useful. Beyond conforming to testing vendors restrictions, it may offer a way for schools to secure sessions against student use of generative AI tools when teachers want to restrict access for live and in person assessment sessions. I learned something working this out - thanks. I just wish I could have found the proper syntax for
?fullscreen=true. For a sign, it would be a lot cleaner if the top menu bar can be made to go away.