Schedules Direct Warning: Current Status and Best Practices for Jellyfin

[matapan]

I’m currently configuring Live TV on a fresh Jellyfin instance and noticed the prominent warning on the Schedules Direct homepage regarding potential account suspension due to aggressive API polling/DoS behavior.
Since I'm just getting my feet wet with the Jellyfin stack, I wanted to check in with the community on a few technical specifics:

• Upstream Status: Is the current Jellyfin release still exhibiting the redundant JSON-RPC calls that triggered these rate-limiting warnings, or has there been a fix implemented in the EPG provider logic?
  
• Mitigation: If I proceed with the native Schedules Direct integration, are there specific configuration tweaks (refresh intervals, thread limits) to ensure I don’t trigger a lockout?
  
• Alternative Backends: If the native integration is still considered "unstable" by SD, what is the preferred alternative? I'm looking into XMLTV via zap2xml or EpgGrabber, but I’d prefer a "set and forget" solution if possible.
  

Any insight into the current state of the SD-Jellyfin relationship or recommendations for a more robust EPG pipeline would be appreciated.

[JdeFalconr]

I'm also interested in finding high-reliability methods to get TV listings for Jellyfin. OTA TV listings pain was probably the main reason why I switched to Plex but I'd be happy to switch back.