From the Migrating from arcpy.mapping to ArcGIS Pro documentation:
When using the CURRENT keyword in the Python window with ArcGIS Desktop, you sometimes had to call refreshActiveView to force a screen refresh. This is no longer the case with ArcGIS Pro. All arcpy.mp API changes will directly update the application.
It is the last sentence that I believe is relevant here. I may be interpreting the documentation too literally, but in your case you are not making arcpy.mp API changes, you are adding data to feature class.
Without an explicit refresh call or a zoom or pan action, ArcGIS Pro would constantly have to be polling the data source to see if any data has changed. Doing so introduces several questions and challenges. For example, how frequently do you do the polling, every second, half-second? What kind of additional and extraneous network or disk traffic is created by the constant polling?
If you were changing arcpy.mp elements (symbology, map frame properties, changing data source for layer), I am sure the changes would happen automagically. In this case, you are updating data in a data source, and I don't believe that is covered by the automatic refresh.
In terms of refresh, I am not sure if there is some automatic refresh at a designated time interval, e.g., every 5 minutes the screen refreshes no matter what.