These are GraphView APIs. GraphView never got out of the experimental/unsupported stage. It’s being kept alive for now because it’s used by ShaderGraph (and other internal products) but there are no plans to make any non-bug-fix improvements. That said, there’s a dedicated team working on a replacement for GraphView that will be released as a proper graph UI framework. No ETA on that yet though.
2022 LTS (or 2022.2 if you open to betas/non-LTS) has a lot of improvements and fixes around nested InspectorElements. I recommend a look if you get the chance.
Image has always been an odd element. It goes a bit against UI styles driving layout and instead has the content (the image) driving the layout. Unless you’re making an image editor of some sort, it’s recommended to set the size of your VisualElement “images” from USS or from C# (which could still read the dimensions from the image asset first).
Don’t get me wrong, I don’t think it was good to introduce the Image element and then leave it untouched for so long. I’m just adding some context on why this controls has not seen a lot of updates. Could change in the future.
We are aware. It will come. It’s slowly making its way up the backlog.