Inability to create a custom binding from scratch

[YohDeadfall]

Prior v11 it was possible to create a totally custom binding which I used in my own project for things like:

var child = new Child("foo");
var parent = new Parent(child);
var target = new TextBox { DataContext = parent };

target.Bind(
    TextBox.TextProperty,
    KineticBinding.TwoWay(source => source
        .Select(source => source as Parent)
        .Property(source => source?.Child)
        .Property(source => source?.Text)));

The code above was able to create a binding listening to DataContext changes, trying to cast its value to Parent and then accessing Text property of an object stored inside Parent's Child property.

Is it possible to implement the same thing now? I though about supporting XAML compiled bindings for my project, but I cannot get how to do that without the ability of making a totally custom binding.

I can add an extension method to AvaloniaObject to make code first binding creation easier for instances, but again, it won't work for styles and templates where the source is taken from the target object. XAMLIL perhaps uses the internal IBinding2 or abuses the private member access in any other way, but I don't want to play with IL and instead I want to generate C# code for bindings instead while feeding back to the Avalonia build task altered XAML files where all Kinetic bindings are replaced by the generated markup extensions producing a binding expression or something like it.