Our C++ API offers the following funtionality:

namespace Noesis::Studio
{

/// Load a Studio project from the given project file and create its visual tree
NS_GUI_STUDIO_API Ptr<FrameworkElement> Create(const char* projectPath, const Options& options);

/// Save all unsaved changes made in the given Studio project
NS_GUI_STUDIO_API void SaveAllChanges(FrameworkElement* studio);

/// Discard all unsaved changes made in the given Studio project
NS_GUI_STUDIO_API void DiscardAllChanges(FrameworkElement* studio);

/// Request Studio to open a file if it exists in the project
NS_GUI_STUDIO_API bool OpenProjectFile(FrameworkElement* studio, const char* path);

/// Updates Studio theme
NS_GUI_STUDIO_API void SetTheme(FrameworkElement* studio, bool darkTheme);

/// Clear Studio's type cache
NS_GUI_STUDIO_API void ClearTypeCache();

/// Populate Studio's type cache
NS_GUI_STUDIO_API void PopulateTypeCache();

}

The C# API (NoesisStudio.cs) offers:

public void SaveAll()
public override void SaveChanges()
public void DiscardAll()
public override void DiscardChanges()

For this task, we need a specific list of functions that you need.

As an initial example, we would like to request a few APIs that could help us handle refresh and reload cases:

bool Studio_ReloadFile(void* studio, const char* path);
bool Studio_IsFileDirty(void* studio, const char* path);
bool Studio_ReloadResources(void* studio);

We would also like to ask whether manually reloading resource dictionaries or global resources, such as GlobalResources.xaml, would be feasible or useful.
We are not sure whether this should be handled through a separate API or as part of a general resource reload operation.

The purpose of these APIs is to handle edge cases where changes made in the Unity Editor or an external text editor are not immediately reflected in Studio.
As a current workaround, we are using a custom Unity Editor extension to restart Studio when necessary.

These are only a few examples of the APIs that could be useful.
If there are other lightweight internal functions or hooks that could be exposed with relatively little effort, we would be happy to use them manually as needed.
We would also appreciate any guidance regarding which approaches are recommended based on the Studio architecture and engine policy.