Talothral Few (non-game breaking) bugs I noticed (and a suggestion):
In update5.rpy line 869+, there's a typo on the variables (u5_MaervaAnswer instead of u5_MaevraAnswer). There's a "Let's fix some shit" comment about it in variables.rpy, so I'm guessing you know this. But update10.rpy (lines 607+) checks for the untypo'd version which never gets set by the player so it always has the default value of 4. Doesn't break anything, just some wrong dialogue. Simplest solution would be to change the checks in update10.rpy to the typo version and use that going foward (assuming it ever gets checked for again). You could also
In update6.rpy, line 487, it's missing a "jump u6_Empress_Time" right after it. Also doesn't really break anything, but it means that whoever reaches that point is on a path where
Lian is dead and since there's no jump the game just slides down to the next available bit of script which is...
label u6_Lian_is_alive. Oops.
In secrets.rpy, line 194, "if persistent.u7_secret2" should be "if persistent.u7_secret3". Again, doesn't break anything but if anyone checks the secrets page after unlocking u7_secret2 (and before unlocking u7_secret3), they'll be confused about not being able to click the newest unlocked (but not really unlocked) thumbnail for the full size.
And the suggestion is about the Scene Speed setting which I found somewhat... useless. Aside from it not affecting the sex scenes (which would be a bit more effort to fix than I felt like putting in), it can't be set to something between 0 and 1 second. I find a 1 second pause to already be a bit slow for what it's used for (and I can't imagine anyone ever wanting a 10 second pause). So I changed it (screens.rpy, line 1368) from
bar value FieldValue(object=persistent, field='pv', range=10.0, style=u'slider', offset=0, step=1.0, force_step=True)
to
bar value FieldValue(object=persistent, field='pv', range=2.0, style=u'slider', offset=0, step=0.1, force_step=True)
This allows the value to be set all the way down to 0.1 (I personally settled on 0.4). The only problem is that if it gets set to 0/paused, then it only does whole number steps again for some reason, until you max out the bar at which point it can do 0.1 steps again. I set the range to 2.0 so that it'd be easier to select the value I wanted.