i know exactly what you mean now. one of the best features about puppy was the simplification and friendliness of things like that. it should be possible (and maybe even desirable) to make tc more like that in the future, and i think suggestions for making things like that more friendly are a good contribution if thought out well.
as long as keeping things good under the hood is the first priority, it should be easy to implement friendlier messages and setups, but there are other times when it's nice to have no-bs for the experienced user also. xsetup.sh is not as "busy" as the setup in puppy last time i saw it, but it's reasonably friendly.
because puppy uses scripts, it's easy to have people that don't know any "real coding" make dialogs friendlier without having someone do it for them.. tc seems pretty intent to avoid most of those scripts in favor of c apps, but this doesn't apply to the startup. it does mean that people that prefer everything in gui form may use another distro that spends more megabytes on a core that uses gui for everything. so focusing on that as much as puppy does may be targeting an audience that would prefer to use something else for other, similar reasons.
it still might be worth making the startup a little more friendly in the future. it may depend on different things, how you make tinycore more friendly may differ from how you make puppy more friendly, since you're trying to provide friendly access to two quite different things. where a text menu is not too intimidating, i'd like to make the text as friendly as possible without annoying experienced users. at its best that's an art as much as a science. new features usually take more than one attempt before they are sufficiently friendly, even in puppy.