Yeah. I fail to see how it could even be true on a conceptual level.
If it were true, what would happen on that day, or probably a few days prior, is that there would be many new Bitcoin forks that use the same transaction history (and thus the same balances) as Bitcoin. After possibly a short scramble and chaos, one or potentially multiple of those forks would then be seen as the Bitcoin while the rest fade to obscurity.
Cryptocurrencies, especially big ones, fork all the time. All it takes is an individual who wants to make a fork. Yes, that means if you have any currency on that chain before the fork, you'll have that same amount on both currencies after the fork. In the rare case where both blockchains after the fork hold any value/respect though, this gets EXTREMELY funny if someone had an NFT on that chain before the fork. Now they have two NFTs (one on each side of the split) and could sell them to separate people, or keep one and sell one, etc.
For clarity: when I wrote "fork" above I was talking about "hard forks" specifically.
This sounds to me like you could benefit from mentally using the information hiding principle for your functions. In other words: Outside of the function, the only thing that matters is "what goes in?" and "what comes out?". The implementation details should not be important once you're working on code outside of that function.
To achieve this, maybe you could write a short comment right at the start of every function. One to two sentences detailing only the inputs/output of that function. e.g. "Accepts an image and a color and returns a mask that shows where that color is present." if you later forget what the function does, all you need to do is read that one sentence to remember. If it's too convoluted to write in one or two sentences, your function is likely trying to achieve too much at once and could (arguably "should") be split up.
Also on a different note: Don't sell your ability to "cludge something together" short. If you ever plan to do this professionally or educationally, you will sadly inevitably run into situations where you have no choice but to deliver a quick and dirty solution over a clean and well thought out one.
Edit: typos