I've run into this situation before as well. And what I understand is that the JTAC recommended version is an independent determination by the support unit without any regard to EOS/EOL status.
They have some kind of internal process based on actual customer call levels and serverity of issues that feed their recommendation. And they do not adjust this with regard to availability of the release due to EOL of the version.
So from a practical standpoint we users need to choose to run the recommended version or keep up with the current version of code when these transitions are out of sync.
One factor to remember is that the JTAC organization will NOT shut down your support request ONLY because you have an EOL version of Junos. So if you keep the recommended version beyond the EOL date you can still open tickets and get support on devices with a contract.
But if the specific issue you report in that ticket is covered by a known PR bug then you will be simply told to upgrade for that ticket.