Yes, I hope Epic will look into this. Since the bug has quite a few votes and is still unresolved, maybe we should just submit more individual bug reports about this to make a statement on how problematic it is in the long run. The plugin I’m working on for a company right now forces the user to restart the engine upon reimporting data. That’s not because the data doesn’t get reimported, that works nicely, but the blueprints accessing said data just stop working if we don’t force the user to do that.
Users want easily accessible solutions, not some tech mumbo jumbo explaining they have to recompile their affected blueprints. A forced restart is easier, but at the same time shouldn’t be necessary in the first place.