SettingsGroup class is the foundation class for working with settings in Studio. Being the foundation also means that the class itself is agnostic to any higher level concepts like project, files, translation memories or terminology. Based on this adding the 2 properties suggested by you the class will become project specific which is not good for places where it's used for different things. The solution is to either work directly with it or to inherit and create your custom typed settings (actually this is exactly what we did in our sample app for the batch task api). 

If you need project information in your settings page you can use the integration api to obtain the current project from there the files that are part of the project. The implement your custom settings that would hold the information your want.

SettingsGroup class is the foundation class for working with settings in Studio. Being the foundation also means that the class itself is agnostic to any higher level concepts like project, files, translation memories or terminology. Based on this adding the 2 properties suggested by you the class will become project specific which is not good for places where it's used for different things. The solution is to either work directly with it or to inherit and create your custom typed settings (actually this is exactly what we did in our sample app for the batch task api). 

If you need project information in your settings page you can use the integration api to obtain the current project from there the files that are part of the project. The implement your custom settings that would hold the information your want.

Adding the 2 properties to the base settings user control might be something that we could add in the API. Not sure yet how much value will bring since it's just a few lines of code to get them from via integration API. Let's see what others have to say about this.