I don't understand what you're asking about or for?
Are you sure you mean MonoGame and not Mono?
Assuming you do mean using these things in MonoGame:
Why? is a far more important question than if? or could it be done?.
UrhoSharp is just a wrapper around Urho3D (and frequently out of date by a few weeks, though that should be moot with development slowing down as Urho3D is largely done at this point). There's no point in trying to utilize it within MonoGame, the two would be stepping all over each other.
I suppose you could use a headless context to use Urho3D's logic and MonoGame for rendering and audio - it'd be a lot of hassle for little gain.
Having taken two projects of reasonable size that were using Urho3D (C++, not UrhoSharp) for rendering and ported them over to MonoGame - I doubt it's viable at all.
Cocos already has Cocos2D-XNA which works with MonoGame, although it's long out of date - probably not far enough to be difficult to update.