Thank you for your response! Although of course, really not what I had hoped to hear. This basically makes inline strokes unusable.
I have used different (both paid and open source) vector manipulation software in the past and none of them had this issue, but I guess it comes down to this:
So why is it that way? I guess there are are plenty of good reasons to do it this way (and accept other downsides therefore).
Thank you for this possible workaround, that's not usable in a professional environment though, I don't really want to trade one bug for another.
I guess for now I just have to avoid inline strokes completely...