Refactor Redundant Settings Hooks in Composables Folder

### Clear and concise description of the problem

I would like to propose a refactoring of the composables folder's settings hooks as I believe they currently contain redundant code.
In the composables folder, there are multiple setting hooks that appear to have similar functionality and may be redundant. This redundancy can make the codebase harder to maintain and extend.

### Suggested solution

I propose refactoring the composables in the `settings` folder to streamline and eliminate redundancy.

### Alternative

One alternative solution would be to leave the code as it is. However, this may lead to ongoing maintenance challenges and increased complexity over time.

### Additional context

_No response_

### Validations

- [X] Follow our [Code of Conduct](https://github.com/kirklin/.github/blob/main/CODE_OF_CONDUCT.md)
- [X] Read the [Contributing Guide](https://github.com/kirklin/contribute).
- [X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Start by inspecting the composables/settings folder and inventorying the settings hooks to determine which functionality overlaps. The issue provides no named files or tests; done would require a defined refactoring scope, removal of confirmed redundancy, and preservation of existing settings behavior.

Written by the indexing model from the issue text.