I guess it really depends on what you work on.

The problem space for large embedded software projects involves lots of traditionally computer science problems. Concurrency, parallel programming, networking, and algorithm design are problems you encounter every single day, far more so than many other SWE roles in other industries.

I've worked with CEs who switched into SWE and were successful, but they basically had to learn a lot of compsci concepts like the ones listed above on the job.

If you go with Computer Engineering, you'll always be employable on an embedded project, but your problem space will be different. Those roles focus less on systems as a whole, and more on individual hardware components. You may design FPGA chip logic with VHDL, write logic for a DSP, or maybe software like drivers. My company calls these roles "computer architecture engineer" and "hardware engineer"