Indeed you can convert any model of an agent into a utility-based model by an I/O-based "wrapper" of it - as described here.

You keep repeating this Texas Sharpshooter Utility Function fallacy (earlier appearances in the link you gave, and here and here, of observing what the agent does, and retrospectively labelling that with utility 1 and everything else with utility 0. And as often as you do that, I will point out it's a fallacy. Something that can only be computed after the action is known cannot be used before the fact to choose the action.