You are exactly right and this is typically the norm in the VFP world. You can definitely create an "i" layer if this is your desire. But this is not really as necessary as it was in VFP for a number of reasons. The primary reason has to do with event handling. Most everything that needs to be "overwritten" in VFP required a method override in order to achieve a different result. The beauty of .NET and StrataFrame is event handling. You can manipulate and mold your application to your needs through events rather than inheritance...at least as far as the "i" layer is concerned. In fact this is what we initially did early on just out of habit, and if you use frameworks that require method overrides, then this is a must. But in an event based environment, this is another nice feature that saves the developer time.
If you have the desire to do this, then it is a very easy process. Simply create an "i" layer class for each control and inherit the control.
FYI, do not use "i" as your prefix. In .NET this is standard prefix for an interface. You will want to choose something else to reduce confision later on.
Example
Public Class MyTextBox
Inherits MicroFour.StrataFrame.UI.Windows.Forms.TextBox
End Class