Yes, you can set the context property to 'private'. This means that all context constraints are dropped, but you can still use the '[%CurrentObject%]' token in your xpath constraint to refer to the object in the enclosing dataview.
Example: [RefToDataviewObject = '[%CurrentObject%]']
To add to what Johan said, if you set the context property to 'private' you can still pass on enclosing context by adding an invoke button with "Pass enclosing context" set to true, this way you can still use the enclosing context in a microflow.
It's not clear what you want. You want to drop the context of the Dataview, and you want to contrain the Datagrid on the Dataview object. Can you explain what you want to constrain on which object?
Maybe you can use a XPath constraint on the Datagrid.