You could also try to do this the other way around. The view is 'fixed', and you want to have the node remain editable.
It appeared this did not work the way I had in mind. You want to show the view on that specific page only and because in views there is no relation between the users and the specific node, so there is no possibility to show the content only on the given node id (the view will be attached to all nodes). EVA is a great module for situations where there is such a connection though.
For example, you might make a View that displays posts with an 'Author
ID' argument, then use Eva to attach the view to the User entity type.
When a user profile is displayed, the User's ID will be passed in as
the argument to the view magically.
Original answer
By creating a basic page with your introduction text and using Entity Views Attachment (I have not tried the 8 version, but for Drupal 7 it worked nice). You configure it from within views, and then choose to attach it to the node. The node remains editable as every other node.
New answer
Since EVA is not a good solution. Let's make a block. If you create a view block that lists your users. Place the block below your content block in the blocks configuration and then change the visibility preferences. Just enter the path to your content (/node/1
or something similar. It is favorable to use the node id, because the URL alias can change more easily.).
A lightweight alternative could be to use the Global: Rendered entity - Content
display in the views header area. This will allow you to embed the complete node in the view. But in this case you will have access to the node via its regular path and the path of the view, which might be undesirable.