Yeah, I think this will work out for the best. I’ll go ahead and mark this solved even though technically I’m still unsure why it was actually happening. But since there’s an obvious and preferred method of rendering which avoids the issue in the first place, that’s fine.
Now, time to go refactor my SpriteDispatcher class for the 4th time in the last 2 days.
Thanks again for your insights!