Generally speaking, a college minor isn't worth much as "authentication" of anything. Minors don't usually have enough depth/intensity to prepare students for much professionally, and sometimes even listing a minor is viewed negatively, as a frivolous distraction that took your full focus away from your major.  The value of a minor is mostly to the student, as a way of organizing studies around a secondary important interest/focus, or of testing whether that's an area you might want to study at the graduate level.  But very few prospective employers are even going to take note of your minor, let alone use it in any sort of comparison of qualified applicants or in judging the strength of your computer programming skills.  By the time you have a few years of professional experience, your undergrad minor is the sort of content you'll probably be cutting from your resume for space anyway, as your "Experience" and "Professional Certifications" categories begin to feature more prominently than your "Education" category. 

If this extra semester will be valuable to you for your own interests and education, and if you'll still feel engaged with the academic subject matter, then that might be a good reason to stick it out.  But if you're just doing it in order to look more "legitimate" on paper then its value doesn't justify the tuition and the loss of your potential earnings in the work world for that extra semester.

If you intend to stay in architecture and aren’t a trust funder do the thing that saves you $$$ which would be graduating early. If you ever want to afford a middle class life, drop the architecture fantasy taught in schools and major in comp sci. You can retire early and pursue architecture as a hobby later. You’ll never afford a decent retirement as an architect. The industry is dying. Consider yourself blessed if you have the mental bandwidth to enjoy coding at all because few do.

neither are real-world skills and neither are going to be useful after the crash

Short answer, keep the minor. Especially if the program is reputable. Review your school salary surveys for recent grads by major. Architecture in industry is very different from school.

I know people who switched from Architecture and now code. They took coding workshops and used projects as their portfolio to get in on ability. Why not do it while in school? 

Well, now i’m even more confused than I was when I posted this.

There are lots of sweeping generalities and stereotypings in this thread, so here's one person's anecdotal experience: I have 20+ years of experience and make about 30% more as an architect than the average computer programmer at the same level in their career makes in my location, which has been the case since around the mid-point of my career-so-far.  This is almost certainly not the case for most entry-level architects - and that does obviously have an impact on young architects' abilities to save and invest.  From a financial standpoint I'm not going to end up eating pet food in an RV park in Arkansas.  I minored in a vaguely related field, and nobody ever cared one way or the other and it affected nothing, including how long it took me to graduate.  If it's going to make you pay for another semester then drop it.
Most of the computer programmers I know work far longer hours than I do - one of them keeps most of his clothes in a bin under his desk at work because he sleeps and showers there more days per week than at home.  I have a sanitation worker friend who makes more money than I do and usually works far fewer hours.  You can have a decent work-life balance in any of these careers - or you can work crazy hours in any of them - it's not really as career-specific as many on this forum would have you believe, it's worker- and employer-specific. 
Your minor is unimportant and hardly anybody will ever care if you had one or what it was. 
Which career you pick is more important, but not forever fixed and unchangeable.
Do whichever feels more right for you now, and rethink if/when necessary.

I minored in compsci. In some cases it was a plus, other cases it didn't hurt. I don't see how this hurts you unless it is a big financial burden.

You never know when this stuff will come up. Might help you get your foot in the door at a startup or something. At giant corporate companies, sometimes it does matter if you have this stuff listed in your HR profile.

As for comments about whether you will be competitive in CS/IT jobs -- there are a whole range of CS and IT jobs and not all of them require top-tier skills... Sure, you won't be qualified to jump into hardcore backend development but that isn't what you're trying to do anyway, right?