I always run my game at 10 or 12 via iNeeds, but there are some issues that I am starting to attribute to me deviating from default timescale, glitches mostly involving NPC activity:
[*]They tend to stand around more, inactive
[*]Navigation weirdness, clusters and clumps of NPC's
[*]They have can have strange schedule quirks: Riverwood seems especially susceptible to this issue; the children NPC's stay up way past their bedtimes and stand in the road...since Riverwood normally reverts to the default timescale regardless, I wonder if iNeeds timescale script is manhandling the timescale situation and thus borking things up a bit.
[/list]Much of these issues aren't that noticeable if you just pass through an area, but if you dawdle and observe, you start noticing the weirdness.
I will (once more into the breach!) be starting a new play through. (I have given up on SkyRe for the moment...way too many compatibility issues and patch maintenance for my taste)
In my new game I will reluctantly use the default game timescale and see how I fare.
AFAIK, all iNeeds does is set the timescale for you, with the same functionality as the console command, [font="'courier new', courier, monospace;"]set [color=#00ff00;]timescale to xx[/color][/font].
With the console command method, anyhow, the timescale will remain constant, so I'm not sure why you'd think Riverwood reverts the timescale to the default 20 value, but next time I'm in Riverwood I'll check on that using the [color=#00ff00;][font="'courier new', courier, monospace;"]show timescale [/color][/font]command.
In my new play through, I'm trying out a timescale of 10, and I have to say that I'm also noticing what seems to be too many NPCs standing around with nothing to do, though not just at nighttime. Same thing with groups of mindless loitering NPCs. Up to now, I hadn't thought of the possibility that all might be related to the timescale setting.
The timescale can be changed at any time, as the dynamic timescale mod shows, so I think we should try changing it to something low and back to default, to see if these odd NPC behaviors are resolved with the default 20 value. I have to assume it would be a good idea to do that when far away from the places where we have observed the problems, and also wait a few days (at least) for things to "flush" out before going back to check.