It does appear that the undocumented api that nitter uses still works and is unblocked by this change as I've been able to access twitter through nitter.
No, it was also working with the self-hosted nitter instance I was using which should have almost nothing cached. Double checked with a new tweet posted in this thread.