3: True. x86 would be better, but that doesn't mean that NVME is of any use on a router like that. Like I said: it's too fast and too expensive at any size compared to alternatives. And not easy removable.
8: I'm not aware of any problems. Why would TLS and HTTPS not work? AFAIK, when NTP is not yet up, OpenWrt sets system time to the timestamp of the most recent saved file. That is good enough not to run into "certificate not yet valid" situations. And what HTTPS and TLS are you talking about? DNS over <something> won't work until WAN is up. When WAN is up, NTP is up too.
5: I don't. What good is a slow cheap router if I need another device next to it? Might as well put an old laptop/desktop as router instead.
Lots of routers are supported by OpenWrt, until they aren't. I already mentioned mwlwifi - they were the best routers, most recommended, until that driver was abandoned. Soldered wifi from another manufacturer won't change the situation. Works today; crashes tomorrow.
8: I'm not aware of any problems. Why would TLS and HTTPS not work? AFAIK, when NTP is not yet up, OpenWrt sets system time to the timestamp of the most recent saved file. That is good enough not to run into "certificate not yet valid" situations. And what HTTPS and TLS are you talking about? DNS over <something> won't work until WAN is up. When WAN is up, NTP is up too.
5: I don't. What good is a slow cheap router if I need another device next to it? Might as well put an old laptop/desktop as router instead.
Lots of routers are supported by OpenWrt, until they aren't. I already mentioned mwlwifi - they were the best routers, most recommended, until that driver was abandoned. Soldered wifi from another manufacturer won't change the situation. Works today; crashes tomorrow.