UPDATE!!!!! So, this happened. AGAIN. I was irritated b/c I had just selected my beautiful team for raid and about 10 minutes prior to hopping into DS10 with my guildies for the first half of the raid, I noticed Kasha (Loque) stealthed and had her bar wonky and her talents reset.
I SHOOK MY FIST!!! My whole team! WHY!!!!!
Since this is a second occurrence, I put in a ticket. Fab respond time, and I even said they didn't need to contact me back if they didn't want to. The pertinent section of the email I received about this issue is as follows:
After some research it appears the issue you are having may be related to your User Interface (UI). This applies whether you have a custom UI or not. To help resolve this issue we recommend the following steps:
1) Exit the World of Warcraft to your desktop by logging out of the game and exiting.
2) If you used an "installer" for a custom UI, see if it has an "uninstaller" and use it.
3) Inside the World of Warcraft Program Folder, rename the "WTF," "Cache," and "Interface" folders to "WTF-Old," "Cache-Old," and "Interface-Old."
4) Restart your computer.
5) Make sure that you are using WOW.EXE or LAUNCHER.EXE to start the game. Please do not run any UI installers beforehand, as we want to eliminate them as part of the issue.
6) Upon launching the game, you should see the Intro cinematic movie and be prompted to agree to the Terms of Use. Once you authenticate past the login screen, the "AddOns" button should no longer be visible at the lower left corner of the character selection screen. Both points mentioned previously must hold true if you should complete the aforementioned steps correctly.
Note: Please also note these folders contain UI addons as well as some UI settings. However, custom macros and keybinding are saved server-side and will not be removed.
JUST IN CASE SOMEONE ELSE HAS THIS ISSUE! I'm trying what the lovely GM suggested.

If you're curious, I run with DBM, TotalRP2, Recount, GTFO as my addons. I don't have custom UI-ness outside what those addons provide. Here's to hoping this is the solution!
I'll of COURSE let you know if the issue comes back and what we discover at that point.
