A couple of things...
1: Great scene compositions... You will do fine there. Less can be more. Easy to do with first-person perspective.
2: Admit to nothing... For all the world knows, it is a friend doing renders for you.
3: If you stay vanilla, and sex is just a small component of the story, it is almost safe to post anywhere. As long as the models clearly look 18+ and you don't breach any kind of "incest" paths. (You can even post it on the RenPy forums and the library there. Though, they tend to only like "completed games" in the library.)
4: Genesis 3 models (Which are Generation 7 characters), may render a little faster. They also have the greatest majority of "decent" supporting assets, available. Genesis 8 (Which is actually Genesis 3 with eyelash tweaks, dubbed as Generation 8 characters), have a LOT less "fitting" assets. Though, most are close and being converted to the, um... deformed Gen3 models, dubbed as Gen8. (Another cluster-fuck idea from Daz3D.)
5: Pubes on skins... That is a shot in the dark. Daz doesn't allow previews of genitals in the store, so you honestly have no clue what you are getting, until you get it. They couldn't be any more unprofessional about it. Professionals don't resort to "if it's safe for kindergarten, then it's safe to preview". You can do some manual touch-up photoshop work, or poke around until you find a skin without built-in pubes painted on the skin. (Kindly, most NEW creators are not adding pubes to the skin itself. Now they need to remove eyebrows and makeup, and the greater majority of the professional world will start taking those models seriously into consideration.)
6: TLDR stories are great for TLDR readers. You can use a little trick in RenPy, to shorten TLDR text, by simply adding a "Choice" to "pry deeper". Feed them the critical things first, and create levels of extra content for the TLDR story readers. You can also give them a special bonus, for reaching the ends of the TLDR context... As long as it doesn't ruin the actual story-line.
7: Be sure to make it clear as day, that the story is about to branch-out into a non-returnable fork. Even if you have to throw a narrative just before a major choice. No-one like to select "have coffee with Diana", or "have lunch with Sue", and have that hidden choice end-up in a game-breaking fork. (Game breaking, if they can't really tell that is what led to the path split.) I see stupid crap like that all the time, and it leaves me shaking my head as to what they were thinking. Such innocent or unclear actions, dominating the protagonists life. (Obviously, they put things in there, because they could, and didn't think to ask themselves if they should. Like they were running out of ideas, and just filled-in some random blanks.)
8: Don't be afraid to re-write the introductions, until it is right. But, eventually surrender to whatever you put, as being right. If you keep going back and changing things in the beginning, it kind-of forces everyone to replay it from the beginning, each time. Old saves don't work right, and without reading the things you changed, the preceding story from the save-points that still work, will just not make sense.
9: If RenPy ends-up boggling your brain, when it comes to story-flow... I suggest looking at "TWINE", to assist with your branching. It makes a quick and dirty thought grabber, to help remind you where you were originally headed. Since concepts change and new ideas can sometimes thwart original intentions. (You can jot-down notes about RenPy in Twine too... Like jump-points or search text, for easy locating within RenPy, from Twine. Because non-linear pathing can get ugly fast, in RenPy, with linear code.)
10: Looking forward to your TLDR game. (If you can't already tell.)
