RealBazinga

Yes, that is correct. For testing purposes you might not need your plugin to be loaded by LSPDFR though, so you can test your functionality like a normal plugin before making it a callout. You could also bind the two commands to one key to quickly reload your changes if you wish to keep it a LSPDFR plugin. You should also be able to manually register your callout with LSPDFR using the RegisterCallout function when loaded directly as a plugin and not via LSPDFR. That might require you to add an assembly resolve handler though to ensure you are pointing to the right LSPDFR instance instead of attempting to loading it again.