The short answer is no, this is not possible without code. In fact, even in code you cannot instruct Test Studio to execute specific non-coded steps. In code it's possible to achieve the same net effect by doing everything
in code, or use code to run whole subtests i.e. our Test-as-step feature via code.
Now back to a high level view, most of the time when we hear such a request we discover the tester is trying to implement two different test cases into one test, where one test case is a description for testing one specific behavior or feature of the application. We're a firm believer that every single test case deserves it's own test. This is the reason we don't support what you're asking for.
The main problem the tester runs into by implementing two test cases in one automated test is that when the test fails you don't know if feature A is not working or feature B. You have to spend additional time studying the results to find out. But if every test is only testing one feature, you know instantly which features are working and which are broken simply by listing which tests are passing and which are failing.
The other complication is the structure of the test itself is more complicated. This makes it more difficult to maintain as the application changes.