True, but it seems like it has some manner of keeping track of time when the unit is off that Raspbian can keep track of. The Raspberry Pi is connected to a university network that has a number of network restrictions, one of which being the blocking of anything to do with NTP, so I set the time manually with
sudo date -s "$(wget -qSO- --max-redirect=0 google.com 2>&1 | grep Date: | cut -d' ' -f5-8)Z" once, and when running Raspbian, if I shut down the Pi, the unit keeps track of the time as long as power is supplied to the board.
As such, since it looks like Manjaro doesn't seem to make use of that, and since I can't use NTP, fake-hwclock doesn't do the job, since the time lags further and further behind after every reboot (and of course, significantly more so if shut down) since it only saves to a file and then pulls that old time.
The only option that I can see at the moment is using crontab to run that manual time-setting command upon booting, but I've having some issues with it that I haven't encountered before.
It would be good to know why with Raspbian, it keeps track of the time when the unit is off but supplied with power, but Manjaro it doesn't.
As for the time zone situation, I saw a few other posts elsewhere mention making sure that the time zone is set. Originally it wasn't, but it's not like we have time zones spanning weeks, so I don't understand how it would keep resetting to further and further back non-existent time zones in order to put it back to same time back in September every time. Having set the time zone manually made no difference, unsurprisingly.