The difference in battery usage between one launcher and another (aside from animation effects, which eat a lot of battery) is a TINY percentage of what the screen itself uses.
As far as running one launcher and having another one still in memory - Android isn't Windows. It will usually keep RAM as full as possible. If you run Apex, then run the stock launcher (from the app drawer), Apex is still in memory, but it's not using battery. If you then hit the Home button, Apex will just start running.
If running the stock launcher got Apex out of memory (you can't really "remove" an app from memory, you can only overwrite its code with some other code, like the stock launcher), then pressing the Home key would require loading Apex again - which would use more battery.
People worry about apps staying in memory in Android because that's a bad thing in Windows. But that's like worrying about a corroded tiller post in your car because it's dangerous in a boat. Android keeps apps in memory to SAVE battery (and time). You don't care if your desktop has to load Excel from the hard drive every time you run it - the drive is running anyway. In Android it costs battery to load an app from storage to RAM. (And even worse is those "RAM optimizers" that "delete" any app not actually running. That can take a pretty bad hit on the battery.)
Your best bet is to just not worry about things like that - Android has a great memory manager, and will force-kill any app that needs to be gotten out of the way.
Multitasking the Android Way | Android Developers Blog is a great explanation by one of the people involved.