When searching for instructions on how to use a button to cycle through scenes, I always skipped the complex looking solutions and 18 minute long YouTube videos thinking it can’t be that hard, surely? Turns out it is! And it has been for a long time too. If input_select could support key value pairs, it would remove mapping code, avoid bugs and make life so much easier for new-comers to Home Assistant.
Attached below are just a few discussions I found on this subject, many feature requests and even Home Assistant documentation that suggests hard coded mappers from dropdown values. Imagine how simple these solutions in the docs would be with labels and values supported in the input_select. Is it super complicated to fix under the hood?
This feature isn’t wanted, it’s needed! Please!!! 
Discussions:
2018 - Input_select with value and label?
2019 - Map values for an input_select?
2021 - Input_select and input_number display value vs actual value
2021 - Input select labem / value pairs?
Duplicate feature requests:
2022 Add both name and value for the input_select integration options
2022 WTH can't input_select have label and key in options?
2022 Select helper with label and values
Suggested solutions that would be so much simpler:
2018 source being copied still in 2023 - Cycle through scenes with a button? Home assistant - cycle scenes with a single button | tamarisk.it
Home assistant docs: Perform actions based on input select - Home Assistant 中文网
Interesting tid bit, when dropdowns were added to the HTML v2 spec in 1995, they also supported key value pairs.
@123, do you think the title of this feature request is clear enough as to what you are requesting? As a software developer, I might not understand mapper without more context. Could the title be “input_select enhancement - add value to options to simplify mapping” please?