I think that the text input cursor conveys a strong expectation for allowing input, which is potentially confusing here. I think that clarifying where you can type and where you cannot seems more important than emphasising the additional amount of interactions supported. Our observations suggest that without such cursor users were already interacting with links and other elements to inspect them.
I know that a visible cursor in read-only areas is needed for accessibility for some people, but this should be controlled by the browser and the OS settings for all browser areas, and not for this particular element.
(As a matter of fact, I'll be very happy if some day it will be possible to edit the source article straight from Content Translation, because I find things to fix in the source article almost every time I translate something, but it's really not what this task is about, and it's not a high priority.)