Probably, similar fixes can be done - https://developer.blender.org/D16251

I do not see this problem now in Blender 3.4.1. May be close this issue?

probably this is related to HiDPI display somehow? I can't reproduce.

My monitor settings

Ah, I see. Never used that option :)

No wonder seems to be same issue that happens with macOS -- when using with SVerchok.

By default, macOS is 2x screen resolution...

NOTE: I might be the only user of Blender + SVerchok using macOS...

I've tested this more carefully. The node starts to work correctly after removing it and recreating it again. It means that it calls something in its init function. In particular it calls this.

I'm not sure why get_dpi_factor can't be called on each redraw. From my point of view it's just a constant and reading it can't be too expensive especially comparatively to what already is happening in the draw functions.

So the fix should be to include reading ui_scale on each redraw. Probably also some proves, that it does not have significant impact on execution duration, can be added.

P.S. This behavior is related to how it's implemented in Sverchok and is irrelevant to API changes in Blender (though API changes still can have an effect but it might have different symptones).