I looked at the code earlier when you mentioned it, it uses twitter's internal api, requires someone to have one (or probably more) twitter accounts to retrieve the tweets and save them, this could be built into some nostr relay, and it would technically not be hard, it would just need more maintanance than the average relay, and just like nitter's code when twitter changes something, so too would that relay