I have to strongly agree with
@Thraktor, hardware development is an incredibly involved multi-year process and does not just appear as if by magic at the precise time it’s needed; if it did, Wii wouldn’t have been allowed to wither on the vine as it did, nor would MS and Sony launch their new hardware in the midst of a pandemic. Been banging this drum since the idea that Nintendo could just stall the process to delay until 2024 or beyond started being bandied about, because any knowledge about physical product development would suggest it’s a tightly regimented process, with target dates for production and release well in advance, especially the more involved the product is and whether there are supply partners involved (like game developers, for example).
We can actually look at how Switch proceeded to get a really clear picture of how this all shakes out and I wrote a bit about this on Install Base that I’m going to cross-post.
New hardware following Wii U was already being discussed in the same year that Wii U launched (almost assuredly because Nintendo knew it had dead weight on its hands), with R&D beginning in earnest
by the end of 2013, when they had already solidified the hybrid design concept, right down to the detachable Joy-Cons. Here's Koizumi's words on this time period:
So, depending on where you start counting... the timeline was 3-4 years from beginning to release.
The SoC would have likely been chosen in late 2014 or early 2015 at the latest, as the Tegra X1 was first being sampled by Nvidia in 2014 before being officially unveiled at CES in January of 2015 for a Q2 2015 wide availability, as "NX" had seemed to have taken enough shape that Iwata could confidently (albeit cryptically) discuss it a few months after the TX1 unveiling in March of 2015, and dev kits were being reported to exist
in October of 2015 (and quite possibly sooner than that) and demoed to select publishers and devs at E3 that same year, which meant Nintendo would start needing to notify publishers of their rough release window for the device so publishers could set staff requirements if they intended to prep launch software (like NIS, for example) and would need kits to be in developer hands long enough in advance for Nintendo to get and implement developer/publisher feedback (like Capcom's famously fulfilled request for additional RAM).
So while an exact release date would not be available, they would need to provide a semi-accurate window for release 1.5-2 years in advance, at least, probably just a rough estimate with 3-6 months of leeway. And we know they had something far more accurate later on with their announcement in April 2016 that "NX" would release that fiscal year, with HW and SW sales projections making it super-obvious it was not happening during the holidays, so they seemed to have it timed down to 30-60 days a year in advance.
So, if we’re discussing Drake, they'd probably need to know when hardware was going to be released within a 3-6 month timeframe by 2020 at the latest and probably knew the year it would release by the 2nd half of 2019. Not so shockingly, this all aligns pretty closely with the timeline we can see with Switch from the date its R&D began.
And we can see that alignment based on R&D expenditure. Let's see this chart,
courtesy of ZhugeEX. You’ll probably notice something.
Large spike in R&D spending starting in FY03/2014 (which is when it's noted work really got going on Switch R&D), which was persistently up for 3 fiscal years, right up until the fiscal year that featured the launch of Switch, when it levelled off...
... that is, until FY03/2020, when R&D spending saw a massive spike (a 20% increase) and has continued to increase YoY ever since. If we use the same timeline as we saw with Switch and count forward from when R&D expenses spiked, we are currently in the 3rd fiscal year since the R&D spike. Which would mean that R&D expenses should start levelling off in the next few quarters.
Between comparative analysis to Switch’s product development cycle (and, frankly, most other Nintendo hardware over the years, which follows very similar patterns), the Linux commit that indicates a tape-out of T239 and everything else we’re hearing, it’s all pointing to a 2023 release.