There are MTA data feeds, in General Transit Feed Specification format, for program use. Those are for systems that update maps.
The MTA dumped Twitter/X in 2023 because Twitter/X wanted to charge them for using their API, and the MTA refused. [1] The MTA also said that Twitter/X had too much downtime.
When the MTA first got into social media, the person who took the job demanded a desk in the rail control center, so she could see all the displays and immediately hear about problems. If someone mentioned a problem on Twitter, she'd reply immediately. That was the right idea. Few organizations have the guts to put the control room on social media.
[1] https://www.mta.info/press-release/statement-mta-acting-chie...