### Godot version

Godot 4.1-beta2

### System information

Manjaro Gnome, Intel Core i7-11800H

### Issue description

On a relatively modern laptop (Intel Core i7-11800H), in a scene with many scripted nodes (total of 900+ with roughly half of them scripted), adding or duplicating a node freezes the editor for several seconds. Godot 4.0.2 handles such scenes much better!

Here is a flame graph captured while repeatedly duplicating simple Marker2D nodes with Ctrl+D in a complicated scene:
![Screenshot from 2023-06-15 23-54-38](https://github.com/godotengine/godot/assets/2766569/d0019f17-9b82-4a26-9b47-71fa7a3bef3a)

Performance data file to use with hotspot v1.4.1 (relevant data starts at the 75-second mark and lasts about 20+ seconds):
[perf.data.perfparser.zip](https://github.com/godotengine/godot/files/11763700/perf.data.perfparser.zip)



### Steps to reproduce

1) Add 1000 nodes with a script attached.
2) Duplicate a node and witness lags.

Also affects scrolling the scene tree dock.

### Minimal reproduction project

[add_node_lags_repro.zip](https://github.com/godotengine/godot/files/11763731/add_node_lags_repro.zip)

history.push_back(h);
	current_elem_idx++;
}
int EditorSelectionHistory::get_history_len() {
	return history.size();
}
int EditorSelectionHistory::get_history_pos() {
	return current_elem_idx;
}
ObjectID EditorSelectionHistory::get_history_obj(int p_obj) const {
	ERR_FAIL_INDEX_V(p_obj, history.size(), ObjectID());
	ERR_FAIL_INDEX_V(history[p_obj].level, history[p_obj].path.size(), ObjectID());
	return history[p_obj].path[history[p_obj].level].object;
}
bool EditorSelectionHistory::is_at_beginning() const {
	return current_elem_idx <= 0;
}
bool EditorSelectionHistory::is_at_end() const {
	return ((current_elem_idx + 1) >= history.size());
}
bool EditorSelectionHistory::next() {
	cleanup_history();
	if ((current_elem_idx + 1) < history.size()) {
		current_elem_idx++;
	} else {
		return false;
	}
	return true;
}
bool EditorSelectionHistory::previous() {