Some Linux hardcores here might roll their eyes at that complaint, but I’m not afraid to admit that I prefer a GUI.

Even most of the Linux hardcores use a GUI. Living 24/7 in a terminal environment is mostly a sysadmin/programmer flex.

The important thing here is that you were able to figure out how to do what you wanted via the terminal, that's a huge first step since most people just give up as soon as they can't use a GUI (props to you). Now that you know the commands to do what you want, you can now do the most common useful Linux thing: make a script

It sounds like Bluetooth works, but requires a configuration/setting that the GUI developer didn't forsee.

What you need to do is to break down the individual tasks that you have to do in the command line (like, enable/disable bluetooth, connect to a device, etc) and type them into a text file instead (one command per line), add #!/bin/bash at the top. Save the file and make it executable (chmod +x filename). Then you can execute the script by typing (from the directory where the script is located) ./enablebluetooth.sh or ./connecttoheadphones.sh

Once you know the scripts work, you can bind them to a hotkey in Plasma Settings under Keyboard Shortcuts -> Add New -> Command or Script -> select your script, and bind it to a hotkey combo. If you wanted to get a bit more advanced, you could probably create some UI buttons that would launch the script when clicked but I don't know how to do that off of the top of my head.

Once you're comfortable with the workflow of 1. Figure out how to do it in the terminal, 2. Write a script, 3. Make the script convenient to use/automatic then you'll come to appreciate the flexibility of the terminal (because you can put it in a script and never have to use the terminal!)

If you try and run into any issues just let me know and I'll try to get to you pointed in the right direction.