I use scenes, if I get motivated, I'll screen capture a few for you. I generally use them to present choices.
For instance, in the car, I have a scene that I use.
-Put phone in car cradle
-nfc tag turns on Bluetooth, turns off WIFI
-Bluetooth connects to car's bluetooth
This triggers a Tasker event to open the scene. The triggered event then waits for 10 seconds. If the event's timer runs out, I run my default of "Mortplayer" to get music in the car. If I push a button on the scene, the push stops the triggered event and executes the chosen program (sometimes I want to use BubbleUPnP for music (streamed from my house). The coolest part of that scene is it has a toggle button. Default the toggle is off. Touch it and the toggle is on. As part of loading whichever music service, it will load Torque, following if the Toggle is on/off (default is off).
I also have an event that triggers off of long holding the search button. This loads the same event/scene
I also use them for things like a detailed weather display (sometimes during a storm, I like to look at the super fine details of weather information...typically not).
I also use one for my morning alarm. Made the buttons so I really had to be awake to turn off the alarm. I've contemplated adding into the script to make the button move around. Right now it is just small.
When I was messing around with my phone's CPU more, I used a scene to choose settings for the CPU. Overclocked, underclocked, type of clocking (aggressive, or more power economical). I still use that here and there. Mostly when the battery gets low and I know I can't get a charge for a bit. I'll use that scene to program the phone for low performance to try to stretch the power use.
--Dan