Well, I can only tell you that at Google there are no "architect" positions, and people expressing a desire to hold such a position will probably not even get an on-site interview, much less actually get hired. Based on that I would say "no" because you can find senior, high-paying jobs where you code all day long every day,
Personally I find the idea of "architect" to be a bit of an industry anti-pattern. It's a person who hasn't written anything in ten years, essentially. If someone wants to write the design doc and implement the first draft and then other people become interested in contributing to the project, that's just technical leadership. But someone who wants to mostly talk about how they would have implemented something, ten years ago when they still remembered how to code, is useless.
Personally I find the idea of "architect" to be a bit of an industry anti-pattern. It's a person who hasn't written anything in ten years, essentially. If someone wants to write the design doc and implement the first draft and then other people become interested in contributing to the project, that's just technical leadership. But someone who wants to mostly talk about how they would have implemented something, ten years ago when they still remembered how to code, is useless.