If I can be the first to weigh-in, here's my take on it:
1.) A command line tool for the LimeSDR that can operate much like the other command line utilities that exist for the RTL-SDR and HackRF. People seem to gravitate toward those tools for the purpose of seeing how the LimeSDR will react when a command is sent in and what to expect from the LimeSDR. Again, this will give developers a way to write their applications knowing what the outcome will be based on calls (because of the command) to the LimeSDR. If SoapySDR is a companion to that because of ease of developing a command line tool, then that's fine, but clear guidance (and the documentation for SoapySDR exists, but may not be clear how it would relate to the command line tool) should be available to the developers to give them the entire scope of how the command line tool and SoapySDR make the LimeSDR perform as intended.
2.) A simpler form of LimeSuite that has a way to show FFTs like LimeSuite does, but incorporates a tab on the app for command line operation so you can do a command and then see in the GUI what's happening. It's like a step-up of the command line tool that incorporates the graphical elements of LimeSuite.
Having typed all that, think we're all in agreement that GNU Radio Companion or Pothos gives us some power of doing things with the LimeSDR, too - - but what it doesn't do is give us any insight into the API or the calls to/from the API if someone is trying to develop their own apps - the command line tool would REALLY help there. GRC is great for quick research, can compile the flowgraph to Python so it can be exposed that way, but doesn't help when someone is 'rolling their own' C/C++ code for Linux or Windows apps.
Just my 42 cents on the matter... 73 de Marty, KN0CK