I'm rather concerned about this use of the status-declined tag, as it implies a finality that I do not believe was intended but which will definitely be read. From the tag wiki (emphasis mine):
A feature request or bug report is considered declined if the report is reviewed and the site developers disagree that the feature should be implemented or the bug should be fixed.
In the case of feature requests, this usually comes up if the request is counter to site philosophy, if the request is attempting to change behavior that is intentional or even encouraged by the system, or if the request creates greater complexity or problems in the system than it successfully solves.
Rather than outright rejecting the feature request, it seems to me that your intent here was to use this as a "status-declined-but-only-for-now", to indicate that yes, it was reviewed, but no, it's not on the table; a role probably better suited for status-deferred:
A feature request or bug with this tag is something that has been evaluated as positive on potential, but is not present in the current work timeline.
Insofar as you want to keep status-deferred for things that only have an actual chance to be moved on in the foreseeable future, I think the best alternative would be to simply remove the status-review tag from the "declined-for-now" requests entirely. This, at least, communicates that the feature request hasn't been outright rejected, and may still be considered if escalated for review in the future at a better time, but simply isn't on the table right now.
Alternatively, perhaps you can create a new tag (status-somedaymaybe?) to cover this use case, which would mark a reviewed request as being viable (or at least still worth considering) while also refusing to move on it at this moment.