OK, sorry. After the dust has been wiped away, I finally get the hack. My concern is, that whenever you apply the entityselector, you actually get the property suggester instead. Things might get confusing and this might even lead to failing unit tests on the entity selector at some point. Have you tried implementing a separate <code>$.wikibase.propertysuggester</code> widget yet? Overwriting the <code>source</code> option derived from <code>$.ui.suggester</code> should allow achieving that. Having your own widget, we could introduce an option (like <code>propertySelectorWidget</code>) in <code>$.wikibase.snakview</code> defaulting to the entityselector. Your extension would simply overwrite this default option via <code>$.wikibase.snakview</code>'s prototype.
Alternatively, having your own widget, you could overwrite <code>$.wikibase.snakview.prototype._buildPropertySelector</code> (which could use a bit of refactoring for being able to overwrite with slim code). That might be even more appropriate and  would feel more like extending than overwriting functionality like done with the entityselector in the change.
However, if everybody else is fine with the current solution for now, let's use it. In mid-term, there definitely should be a separate <code>$.wikibase.propertysuggester</code> widget. If https://github.com/wmde/ValueView/pull/47 and the corresponding change in Wikibase are merged, we will need to refactor / be able to simplify the logic here anyway.