I love this approach, but a few years ago I tried it very unsuccessfully with my Xiaomi Mi 34" ultrawide.
By very unsuccessfully, I mean that the commands to change input didn't work. I can't remember if they did nothing or crashed the monitor, but subsequent investigation led me to realise I was lucky not to brick it, as some people found certain commands cause non-recoverable issues on that monitor!
So, I suggest caution in the form of maybe checking that others have successfully used DDC commands on your particular model.
That writing isn't the only "thinking" though. Some thinking can happen in the course of generating a single token, as shown by the ability to answer a question without any intermediate reasoning tokens. But as we've all learnt this is a less powerful and more error-prone mode of thinking.
So that is to say I think a small amount of secret reasoning would be possible, e.g. if the location is known or guessed from the beginning by another means and the reasoning steps are made up to justify the conclusion.
The more clearly sound the reasoning steps are, the less plausible that scenario is.
This has really made insurance click for me because while I understand it intuitively, I wanted a more scientific foundation to understand its value.
I think a great illustration is an extreme case. If I have a house and just enough income to cover all my needs and wants (including retirement savings), then depending on my attitude an extra $1000 per year might have no effect at all - I have nothing I want to spend it on and nothing to save for.
But losing my home would still be devastating. So the utility value of the $1000 per year for the rest of my life is low or none, but the utility value of the previously earned money I would lose from losing my house is high.
The lane keep assist in my 2017 Leaf is awful. If I used it, anyone would take me for a drunk driver as it drifts to the edge of the lane and then corrects endlessly.
Thankfully it can be turned off, and it stays off.
By very unsuccessfully, I mean that the commands to change input didn't work. I can't remember if they did nothing or crashed the monitor, but subsequent investigation led me to realise I was lucky not to brick it, as some people found certain commands cause non-recoverable issues on that monitor!
So, I suggest caution in the form of maybe checking that others have successfully used DDC commands on your particular model.
https://github.com/rockowitz/ddcutil/issues/153